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

[Alessio Soldano (JIRA)]

     [ https://jira.jboss.org/browse/JBWS-3007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alessio Soldano updated JBWS-3007:
----------------------------------

    Fix Version/s: jbossws-cxf-4.0
                   jbossws-metro-4.0
                   jbossws-native-4.0
                       (was: jbossws-native-3.3.0)
                       (was:  jbossws-cxf-3.3.0)
                       (was: jbossws-metro-3.3.0)


While I've been doing what's written in the description for the 3.3.0.GA release, I'm moving this to 4.0 for the documentation, as the hudson machine is going to change soon and that's likely to influence this process.

> 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

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