Hi, i've documented the new release process at : http://people.apache.org/~andyhot/tapestry-site/dev/checklist-new.html For comparison, the previous process is at : http://people.apache.org/~andyhot/tapestry-site/dev/checklist.html
The process can be summarized as: 1) mvn release:prepare 2) mvn release:perform 3) Login to Nexus, 'close' automatically created staging repository and note its url. 4) Send vote email ... 3 days pass 5) Login to Nexus and promote the release 6) Generate and upload Binary / Source Distributions (currently needs ant) 7) Once files reach all mirrors, update the Downloads Page Steps 1-5 are really straightforward/automated (meaning that no manual copying of files is needed). The artifacts of step 6 could perhaps also be generated by maven (and thus be staged as well) but i'm not sure if we can spend time on this right now. Because of that (and that's the only difference to the previous workflow), i've moved the Binary / Source Distributions step at the very end, i.e. after the vote has passed. Is that a deal-breaker? The alternative would be to move that step just before step 4. So, please take a look and comment if something needs more explanation or changes. -- Andreas Andreou - [email protected] - http://blog.andyhot.gr Tapestry / Tacos developer Open Source / JEE Consulting --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
