On 10/16/07, Antonio Petrelli <[EMAIL PROTECTED]> wrote: > I can be the release manager if it is ok. I would like to test the release > plugin (and fix the problems that may arise).
That would be great, Antonio! I should mention that right now the Maven builds are not creating the -docs artifact or doing the J4 backports. I don't know if the release plugin is setup to do those too now. (Do we even want to keep running the J4 backport for 2.1? If so, we might want to change the distribution artifact from -j4 to -backport, to match the repository.) Another "sticky wicket" is that the current version number is embedded in the home page for the Struts 2 area: * http://struts.apache.org/2.0.9/index.html We've been editing the docs/index.html file locally to change download label to version 2.0.# (<small>version 2.0.#</small>). Otherwise, when we archive the page, it cites the prior version rather than (what will be) the current version.The index page actually in the repository (rather than confluence), so we could also edit it before and after the tagging. Or, we could stop citing the version number :) I'll be around this week and Monday if there are any questions. Later next week, I'll be at the Ajax Experience in Boston, so I don't know what my availability will be like. Of course, Rainer has been through the Struts 2 release process too. -Ted. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
