All, I am proposing that we change our release process so that we can leverage the Apache instance of Sonatype Nexus Professional. I will personally perform the necessary steps to get the appropriate information documented and the appropriate access granted. I estimate the steps to be as follows -
- Request access to the Nexus repository. I will make sure to gather all of the required details (nexus login, etc.) so that the necessary information can be documented in Confluence, on the following page (http://struts.apache.org/2.x/docs/creating-and-signing-a-struts-21x-distribution.html) - Make any changes to pom.xml files so that the various plugins will know about nexus acting as the snapshot and staging repository - Convince hudson to push snapshot builds to the nexus instance - Update the documentation referenced above Once you have had a chance to review the documentation and necessary steps, please respond with a vote: [ ] +1 Agree [ ] +0 Indifferent, but do not disagree [ ] -0 Disagree, but not sure why [ ] -1 Do not agree, leave release procedure as-is Everyone who has a vested interest is invited to vote. Votes by PMC members are considered binding. A vote passes if there are at least three binding +1s and more +1s than -1s. The vote will remain open for at least 72 hours, longer upon request. As always, the act of voting carries certain obligations. A binding vote not only states an opinion, but means that the voter is agreeing to help do the work -- Wes Wannemacher Head Engineer, WanTii, Inc. Need Training? Struts, Spring, Maven, Tomcat... Ask me for a quote! --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
