[
https://issues.jboss.org/browse/RFPL-1854?page=com.atlassian.jira.plugin....
]
Lukáš Fryč commented on RFPL-1854:
----------------------------------
Pre-release testing means running full automated suite + manual tests (called release
testing right now).
Automated release verification is then running smoke tests (metamer-smoke +
showcase-ftest) on released bits to verify that there are no build/deploy defects.
Improve release process to fix need for respins
-----------------------------------------------
Key: RFPL-1854
URL:
https://issues.jboss.org/browse/RFPL-1854
Project: RichFaces Planning
Issue Type: Task
Security Level: Public(Everyone can see)
Components: administration
Reporter: Lukáš Fryč
Current release process involves:
# diverging release branch
# bumping the version / tagging
# releasing to staging area
# release testing
# fixes + re-spins
It would be great to catch as much issues as possible before releasing to staging area:
# diverging release branch
# building project to separated snapshot repository (Nexus QA?)
# pre-release testing (includes manual tests)
# fixes
# bumping the version / tagging
# releasing to staging area
# automated release verification
In this scenario both, integrity of build and no need for respins will be ensured.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira