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

Re-define QA phase leveraging staging repositories -------------------------------------------------- Key: JBWS-3007 URL: https://jira.jboss.org/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-cxf-4.0, jbossws-metro-4.0, jbossws-native-4.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