[jbossws-issues] [JBoss JIRA] Created: (JBWS-3007) Re-define QA phase leveraging staging repositories

[Alessio Soldano (JIRA)]

Re-define QA phase leveraging staging repositories
--------------------------------------------------

                 Key: JBWS-3007
                 URL: https://jira.jboss.org/jira/browse/JBWS-3007
             Project: JBoss Web Services
          Issue Type: Task
      Security Level: Public (Everyone can see)
          Components: jbossws-cxf, jbossws-metro, jbossws-native, productization
            Reporter: Alessio Soldano
             Fix For: jbossws-native-3.3.0,  jbossws-cxf-3.3.0, jbossws-metro-3.3.0


Now that the new maven repository based on nexus is available, we can finally implement a better QA phase. I'm thinking about providing a proper maven profile for hudson to run against the staging repository. That would allow us to do what follows at code freeze:
- verify all green (blue) on hudson against trunk
- tag every changed components (spi, common, fw, ci, stacks) and mvn deploy them
- close the temporary staging repository/repositories making the artifacts move to the shared staging repo
- quickly re-start hudson against the staging repository
- get a full clear run on hudson (starting with a local repository cleanup)
- promote the artifacts to the release repository

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira