I've just double-checked, and the staged files were released at 29 March 2011 06:21 which is less than a day ago.
The files in the staging repo are dated Fri Mar 25 01:34:08, which is what made me think it was taking too long. So I won't send the e-mail yet. On 30 March 2011 02:58, Gary Gregory <garydgreg...@gmail.com> wrote: > On Tue, Mar 29, 2011 at 9:52 PM, sebb <seb...@gmail.com> wrote: >> >> On 30 March 2011 02:36, Gary Gregory <garydgreg...@gmail.com> wrote: >> > Wait! I'm not done or I'm loosing my marbles... >> > >> > I followed the whole song and dance from: >> > >> > http://wiki.apache.org/commons/UsingNexus >> > >> > It's the last time I'll pick that route. >> > >> > I cannot seem to have published the Maven bits to Maven places. There is >> > no >> > 1.5 here: >> > >> > http://repo1.maven.org/maven2/commons-codec/commons-codec/ >> > >> > Because it is not here: >> > >> > /x1/www/people.apache.org/repo/m2-ibiblio-rsync-repository/commons-codec >> >> Because that is replaced by Nexus. >> >> > What does "Promote" out of Nexus do then? >> > >> > Should I copy the files to /www/ >> > people.apache.org/repo/m2-ibiblio-rsync-repository myself per >> > >> > http://commons.apache.org/releases/release.html >> > >> > under the section "3 Deploy Maven Artifacts"? >> >> No. >> >> > Or will that cause problem with work I did in Nexus (for the last time?) >> >> The staged release is here: >> >> >> https://repository.apache.org/content/groups/staging/commons-codec/commons-codec/1.5/ >> >> It usually takes some time to reach Maven Central, but this does seem >> to be taking longer than normal. >> >> Best to post a question on repository @ A.o - or I can do that for you >> if you prefer, as I'm subscribed already. > > Please go ahead. Thank you! > > Gary > >> >> > Thank you >> > >> > Gary >> > >> > ---------- Forwarded message ---------- >> > From: sebb <seb...@gmail.com> >> > Date: Tue, Mar 29, 2011 at 10:15 AM >> > Subject: Re: [VOTE] Release Apache Commons Codec 1.5-RC1 >> > To: Commons Developers List <dev@commons.apache.org> >> > >> > >> > On 29 March 2011 04:45, Gary Gregory <garydgreg...@gmail.com> wrote: >> >> On Mon, Mar 28, 2011 at 11:21 PM, Phil Steitz <phil.ste...@gmail.com> >> > wrote: >> >> >> >>> On 3/28/11 4:49 PM, Gary Gregory wrote: >> >>> > I am having a heck of a time pushing the release out. >> >>> > >> >>> > I cannot seem to be able to create the sym links per the >> >>> > instructions >> > in >> >>> > http://wiki.apache.org/commons/UsingNexus >> >>> > >> >>> > I cannot get the symlinks.sh script working. I copied it to my home >> >>> > bin >> >>> > directory. When I invoke it, it is not found. Just running it from >> >>> > my >> >>> home >> >>> > bin w/o args does give me the usage I get: >> >>> > >> >>> You need to run it from the dist directory where the links are going >> >>> to be created and you need to give it the release number. See steps >> >>> 1 and 2 here: >> >>> http://commons.apache.org/releases/release.html >> >>> >> >>> Step 2 assumes that the tars and zips have somehow made their way to >> >>> /www/www.apache.org/dist/commons/foo/ >> >>> >> >>> Step 1 provides instructions on how to move things there. I think >> >>> Nexus tries to do this moving for you. >> >>> >> >>> To get the symlinks created properly, you need to invoke symlinks.sh >> >>> with the release number as its command line argument from >> >>> /www/www.apache.org/dist/commons/foo/ >> >>> >> >>> For that to work, you have to have the script available and >> >>> executable. That should happen if you put it in your bin directory >> >>> and do chmod +x on it. Have a look at your .profile file (cat >> >>> ~/.profile). If it does not contain a line that looks something like >> >>> >> >>> >> > >> > PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/games:/usr/local/sbin:/usr/local/bin:/usr/X11R6/bin:$HOME/bin; >> >>> export PATH >> >>> then you need to add that line (maybe minus the games and X11R6 >> >>> stuff) or just copy a new .profile. Let me know if you are having >> >>> problems with this and I will help. >> >>> >> >>> Sebb is right though that you should close the VOTE before moving >> >>> stuff to dist/ >> >>> >> >> >> >> Thank you for the detailed instructions. I am going to go through those >> >> next. >> >> >> >> I must have misunderstood the voting process, which I thought was, if >> >> all >> >> goes well: >> >> - Send a [VOTE] email (this thread) >> >> - Wait 72 hours >> >> - Send a [VOTE][RESULT] email: >> >> >> > >> > http://mail-archives.apache.org/mod_mbox/commons-dev/201103.mbox/%3caanlktikgpm0lo-aoi8wfkjxznoxzodtgza2cwjdcq...@mail.gmail.com%3E >> >> >> >> Is there a [VOTE][CLOSE] email that needs to go out as well after 72 >> > hours? >> > >> > No, but for some reason I did not see the [RESULT] e-mail - sounds >> > like Phil did not either. >> > >> >> I can see that I should have mentioned the vote timeline in the [VOTE] >> > email >> >> as documented in http://commons.apache.org/releases/prepare.html >> >> >> >> But, I used the [VOTE] email template from >> >> http://wiki.apache.org/commons/UsingNexus which contains no such text. >> >> >> >> Sigh, the release process is so obtuse with the mixture of Maven, UNIX, >> >> Nexus, multiple instruction pages, and so on. It is quite discouraging >> >> and >> > a >> >> barrier to progress :( >> > >> > Patches welcome ... >> > >> >> Gary >> >> >> >>> >> >>> Phil >> >>> >> >>> >> >>> >> symlinks.sh >> >>> > symlinks.sh: Command not found. >> >>> > >> >>> >> sh symlinks.sh >> >>> > symlinks.sh: 46: Syntax error: word unexpected >> >>> > >> >>> > I need some UNIX help ;) >> >>> > >> >>> > Thank you, >> >>> > Gary >> >>> > >> >>> > On Thu, Mar 24, 2011 at 9:39 PM, Gary Gregory >> >>> > <garydgreg...@gmail.com >> >>> >wrote: >> >>> > >> >>> >> [VOTE] Release Apache Commons Codec 1.5-RC1 >> >>> >> >> >>> >> Tag: >> >>> >> >> >>> >> >> >>> >> >> >>> >> > >> > https://svn.apache.org/repos/asf/commons/proper/codec/tags/commons-codec-1.5-RC1 >> >>> >> >> >>> >> Site: >> >>> >> >> >>> >> >> >>> >> http://people.apache.org/builds/commons/codec/1.5/RC1/site/index.html >> >>> >> >> >>> >> Binaries: >> >>> >> >> >>> >> >> >>> >> >>> https://repository.apache.org/content/repositories/orgapachecommons-041/ >> >>> >> >> >>> >> [ ] +1 release it >> >>> >> [ ] +0 go ahead I don't care >> >>> >> [ ] -1 no, do not release it because >> >>> >> >> >>> >> Thank you, >> >>> >> Gary >> >>> >> >> >>> >> http://garygregory.wordpress.com/ >> >>> >> http://garygregory.com/ >> >>> >> http://people.apache.org/~ggregory/ >> >>> >> http://twitter.com/GaryGregory >> >>> >> >> >>> > >> >>> > >> >>> >> >>> >> >>> --------------------------------------------------------------------- >> >>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org >> >>> For additional commands, e-mail: dev-h...@commons.apache.org >> >>> >> >>> >> >> >> >> >> >> -- >> >> Thank you, >> >> Gary >> >> >> >> http://garygregory.wordpress.com/ >> >> http://garygregory.com/ >> >> http://people.apache.org/~ggregory/ >> >> http://twitter.com/GaryGregory >> >> >> > >> > --------------------------------------------------------------------- >> > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org >> > For additional commands, e-mail: dev-h...@commons.apache.org >> > >> > >> > >> > >> > -- >> > Thank you, >> > Gary >> > >> > http://garygregory.wordpress.com/ >> > http://garygregory.com/ >> > http://people.apache.org/~ggregory/ >> > http://twitter.com/GaryGregory >> > >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org >> For additional commands, e-mail: dev-h...@commons.apache.org >> > > > > -- > Thank you, > Gary > > http://garygregory.wordpress.com/ > http://garygregory.com/ > http://people.apache.org/~ggregory/ > http://twitter.com/GaryGregory > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
