Maurizio One more thing, the docs aren't accurate, you have to download the assemblies from Nexus, not to use created / uploaded by you as they miss control sums. I've been using the script below to do that:
#!/bin/bash for f in struts*.* do rm $f done wget -erobots=off -nv -i -E -l 1 --accept=zip,md5,sha1,asc -r --no-check-certificate -nd -nH https://repository.apache.org/content/groups/public/org/apache/struts/struts2-assembly/$VERSION for f in *2-assembly*.zip* do mv $f `echo $f | sed s/2-assembly//g` done for f in struts2-assembly-*.pom* do rm $f done Kind regards -- Łukasz + 48 606 323 122 http://www.lenart.org.pl/ Warszawa JUG conference - Confitura http://confitura.pl/ 2011/9/5 Maurizio Cucchiara <maurizio.cucchi...@gmail.com>: > Hi René, > it makes a lot of sense to me. So if there is no objections, I would rename > the 2.2.3.1 branch to 2.2.3.x. > In this way, it makes also sense to allow the maven release plugin to > increment the version in order to prepare for next development iteration. > > Thank you for your suggestion. > Maurizio Cucchiara > > > On 5 September 2011 16:40, Rene Gielen <rene.gie...@googlemail.com> wrote: > >> Maurizio, >> >> great, thanks for jumping in! You've earned your Release Manager Badge >> the hard way, as it is mostly always for the first time :) >> >> While reading your posts and checking [1] I stumbled upon the branch >> name to use. >> >> Actually we should adjust "When a serious security issue arises, we >> should try to create a #.#.#.1 branch from the last GA release, and >> apply to that branch only the security patch." - the branch to create >> would be "2.2.3.x" and not "2.2.3.1" - the latter one will be the tag >> for the version to release. If we would have to roll out another patch >> release, the patch would be applied against 2.2.3.x branch and the >> tagged as 2.2.3.2. So I'd suggest to exchange the cited "#.#.#.1" with >> "#.#.#.x". >> >> Does this make sense to you guys? >> >> - René >> >> [1] >> >> https://cwiki.apache.org/confluence/display/WW/Creating+and+Signing+a+Struts+2.2.x+Distribution#CreatingandSigningaStruts2.2.xDistribution-FastTrackinganImportantSecurityRelease >> >> Am 05.09.11 17:58, schrieb Maurizio Cucchiara: >> > It looks like it works now, thank you Lukasz. >> > >> > Maurizio Cucchiara >> > >> > >> > >> > 2011/9/5 Łukasz Lenart <lukasz.len...@googlemail.com>: >> >> I've messed up everything, I was thinking about JIRA but checked on >> >> Confluence :/ >> >> >> >> Anyway, please check now. >> >> >> >> >> >> Kind regards >> >> -- >> >> Łukasz >> >> + 48 606 323 122 http://www.lenart.org.pl/ >> >> Warszawa JUG conference - Confitura http://confitura.pl/ >> >> >> >> >> >> 2011/9/5 Maurizio Cucchiara <mcucchi...@apache.org>: >> >>> Hi Lukasz, >> >>> I don't know if it will help, but looking at JIRA I realized that on >> >>> the OGNL project (so would you) I have the admin rights which we are >> >>> talking about. >> >>> Maurizio Cucchiara >> >>> >> >>> >> >>> >> >>> 2011/9/5 Łukasz Lenart <lukasz.len...@googlemail.com>: >> >>>> I've asked INFRA if they can create such a group - >> struts-release-manager >> >>>> I have rights to do it, but I don't know how :/ >> >>>> >> >>>> >> >>>> Kind regards >> >>>> -- >> >>>> Łukasz >> >>>> + 48 606 323 122 http://www.lenart.org.pl/ >> >>>> Warszawa JUG conference - Confitura http://confitura.pl/ >> >>>> >> >>>> >> >>>> 2011/9/5 Maurizio Cucchiara <mcucchi...@apache.org>: >> >>>>> Hi Wendy, >> >>>>> I was talking about the 6,7,8 steps listed on http://s.apache.org/hb >> >>>>> and generally everything related to JIIRA, since I have no JIIRA >> admin >> >>>>> rights. >> >>>>> >> >>>>> >> >>>>> Maurizio Cucchiara >> >>>>> >> >>>>> >> >>>>> >> >>>>> On 5 September 2011 01:59, Wendy Smoak <wsm...@gmail.com> wrote: >> >>>>>> On Sun, Sep 4, 2011 at 4:17 PM, Maurizio Cucchiara >> >>>>>> <mcucchi...@apache.org> wrote: >> >>>>>>> Lukasz, >> >>>>>>> I am afraid I am not able to perform the 6,7,8 tasks illustrated >> on >> >>>>>>> http://s.apache.org/rel, since I have no enough karma. >> >>>>>> Which steps do you mean? Any committer should be able to stage a >> >>>>>> release and call a vote. >> >>>>>> >> >>>>>> (There is a 'versions' plugin that can make the version number >> >>>>>> changes, though if you're good at regular expressions your way was >> >>>>>> probably quicker. :) ) >> >>>>>> >> >>>>>> -- >> >>>>>> Wendy >> >>>>>> >> >>>>>> >> --------------------------------------------------------------------- >> >>>>>> To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org >> >>>>>> For additional commands, e-mail: dev-h...@struts.apache.org >> >>>>>> >> >>>>>> >> >>>>> --------------------------------------------------------------------- >> >>>>> To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org >> >>>>> For additional commands, e-mail: dev-h...@struts.apache.org >> >>>>> >> >>>>> >> >>>> --------------------------------------------------------------------- >> >>>> To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org >> >>>> For additional commands, e-mail: dev-h...@struts.apache.org >> >>>> >> >>>> >> >> --------------------------------------------------------------------- >> >> To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org >> >> For additional commands, e-mail: dev-h...@struts.apache.org >> >> >> >> >> > --------------------------------------------------------------------- >> > To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org >> > For additional commands, e-mail: dev-h...@struts.apache.org >> > >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org >> For additional commands, e-mail: dev-h...@struts.apache.org >> >> > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
