You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by Gary Gregory <ga...@gmail.com> on 2011/03/30 03:36:15 UTC
Release hell WAS: [VOTE] Release Apache Commons Codec 1.5-RC1
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
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"?
Or will that cause problem with work I did in Nexus (for the last time?)
Thank you
Gary
---------- Forwarded message ----------
From: sebb <se...@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 <de...@commons.apache.org>
On 29 March 2011 04:45, Gary Gregory <ga...@gmail.com> wrote:
> On Mon, Mar 28, 2011 at 11:21 PM, Phil Steitz <ph...@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+F-@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 <garydgregory@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-unsubscribe@commons.apache.org
>> For additional commands, e-mail: dev-help@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-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
--
Thank you,
Gary
http://garygregory.wordpress.com/
http://garygregory.com/
http://people.apache.org/~ggregory/
http://twitter.com/GaryGregory
Re: Release hell WAS: [VOTE] Release Apache Commons Codec 1.5-RC1
Posted by sebb <se...@gmail.com>.
On 30 March 2011 08:07, Ralph Goers <ra...@dslextreme.com> wrote:
>
> On Mar 30, 2011, at 12:01 AM, Luc Maisonobe wrote:
>
>> Le 30/03/2011 03:36, Gary Gregory a écrit :
>>> 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.
>>
>> For what its worth, for math 2.2 I used a mix of Phil scripts for the
>> beginning and Nexus for the rest, using the wiki as a guideline. In this
>> case the process was a little convoluted, because we create both a
>> trimmed down version of the site to hold only the user guide and to be
>> put in the docs archives, and we create a complete site to be uploaded.
>>
>> For the last release candidate, it worked well. Phil asked me to
>> document it and extend the scripts if needed, and I forgot to do it in
>> time, sorry :-(
>>
>> The one thing I found cumbersome was that part of the process pushed
>> non-maven artifacts on Nexus, that had to be manually moved away.
>> Furthermore, these are what we consider here the real Apache artifacts
>> (i.e. the ones that are available in the download page, not the ones
>> that are at last published in maven repository).
>>
>> I also have some slight concerns using a proprietary product, but as it
>> secures some things as Sebb says, I can live with it.
>>
>> Is it possible to find some intermediate approach, extending Phil
>> scripts, pushing only the maven part on Nexus directly without having to
>> log on Nexus web interface ? The last part (not logging to close the
>> staging area) may reduce the safety we get and risk some spurious
>> publish as Sebb explained, but with several independent scripts, this
>> could leverage the risk.
>
> Is this what you are looking for? http://www.sonatype.com/books/nexus-book/reference/staging-sect-managing-plugin.html
Oh dear. I was hoping that had not been implemented.
Using that plugin means that one can effectively bypass Nexus.
>
> Ralph
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: Release hell WAS: [VOTE] Release Apache Commons Codec 1.5-RC1
Posted by Luc Maisonobe <Lu...@free.fr>.
Le 30/03/2011 09:07, Ralph Goers a écrit :
>
> On Mar 30, 2011, at 12:01 AM, Luc Maisonobe wrote:
>
>> Le 30/03/2011 03:36, Gary Gregory a écrit :
>>> 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.
>>
>> For what its worth, for math 2.2 I used a mix of Phil scripts for the
>> beginning and Nexus for the rest, using the wiki as a guideline. In this
>> case the process was a little convoluted, because we create both a
>> trimmed down version of the site to hold only the user guide and to be
>> put in the docs archives, and we create a complete site to be uploaded.
>>
>> For the last release candidate, it worked well. Phil asked me to
>> document it and extend the scripts if needed, and I forgot to do it in
>> time, sorry :-(
>>
>> The one thing I found cumbersome was that part of the process pushed
>> non-maven artifacts on Nexus, that had to be manually moved away.
>> Furthermore, these are what we consider here the real Apache artifacts
>> (i.e. the ones that are available in the download page, not the ones
>> that are at last published in maven repository).
>>
>> I also have some slight concerns using a proprietary product, but as it
>> secures some things as Sebb says, I can live with it.
>>
>> Is it possible to find some intermediate approach, extending Phil
>> scripts, pushing only the maven part on Nexus directly without having to
>> log on Nexus web interface ? The last part (not logging to close the
>> staging area) may reduce the safety we get and risk some spurious
>> publish as Sebb explained, but with several independent scripts, this
>> could leverage the risk.
>
> Is this what you are looking for? http://www.sonatype.com/books/nexus-book/reference/staging-sect-managing-plugin.html
Almost. As a maven plugin, I suspect it will be difficult to select
exactly what we want and what we don't want on nexus. For example I had
to manually remove the non-maven artifacts (files for the donwload area
and spurious checksum of signature files). With this plugin, I see we
can list what has been uploaded but I don't see how to delete some of
the files before closing the staging area.
Luc
>
> Ralph
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: Release hell WAS: [VOTE] Release Apache Commons Codec 1.5-RC1
Posted by Ralph Goers <ra...@dslextreme.com>.
On Mar 30, 2011, at 12:01 AM, Luc Maisonobe wrote:
> Le 30/03/2011 03:36, Gary Gregory a écrit :
>> 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.
>
> For what its worth, for math 2.2 I used a mix of Phil scripts for the
> beginning and Nexus for the rest, using the wiki as a guideline. In this
> case the process was a little convoluted, because we create both a
> trimmed down version of the site to hold only the user guide and to be
> put in the docs archives, and we create a complete site to be uploaded.
>
> For the last release candidate, it worked well. Phil asked me to
> document it and extend the scripts if needed, and I forgot to do it in
> time, sorry :-(
>
> The one thing I found cumbersome was that part of the process pushed
> non-maven artifacts on Nexus, that had to be manually moved away.
> Furthermore, these are what we consider here the real Apache artifacts
> (i.e. the ones that are available in the download page, not the ones
> that are at last published in maven repository).
>
> I also have some slight concerns using a proprietary product, but as it
> secures some things as Sebb says, I can live with it.
>
> Is it possible to find some intermediate approach, extending Phil
> scripts, pushing only the maven part on Nexus directly without having to
> log on Nexus web interface ? The last part (not logging to close the
> staging area) may reduce the safety we get and risk some spurious
> publish as Sebb explained, but with several independent scripts, this
> could leverage the risk.
Is this what you are looking for? http://www.sonatype.com/books/nexus-book/reference/staging-sect-managing-plugin.html
Ralph
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: Release hell WAS: [VOTE] Release Apache Commons Codec 1.5-RC1
Posted by Gary Gregory <ga...@gmail.com>.
>
> > 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/
>
Still nothing there. :(
Gary
Re: Release hell WAS: [VOTE] Release Apache Commons Codec 1.5-RC1
Posted by Jochen Wiedmann <jo...@gmail.com>.
On Wed, Mar 30, 2011 at 6:03 PM, Phil Steitz <ph...@gmail.com> wrote:
> There is this cool command called "cp" that works very well. There
> is another one called "tar" and even one called "scp" ;) If the
> problem is that we want to be more paranoid than we are with the
> mirrors for the maven stuff, why can't we just get access and copy
> the files we want to put in the staging repo?
Yes, and there is a stupid little thing called "human", which tends to
introduce slight little errors on the way like wrong permissions,
ownership, missing MD5 sums, and the like.
Just believe me, if you did than once with 40 files or so, then you
start to like Nexus and the release plugin real soon.
> Or write a simple
> script that moves the kind of thing that I have sitting now in
> http://people.apache.org/~psteitz/pool-1.5.6-rc2/maven/
> to the "staging repository" and another script or command that
> "promotes" it. It seems ridiculous to me that we need to introduce
> a proprietary GUI tool to just move files on ASF hosts.
That would simply mean to rewrite the release plugin plus maintain it
whenever Apache, Maven, or Commons change their policies. Do you
really think that makes sense?
I am sorry for everyone who's forced to publish a release with Nexus.
But I'm much more sorry for everyone who's forced to do it without.
And, believe me, I've had plenty of both variants as a release manager
for various projects in commons and ws, and Rat.
Jochen
--
I Am What I Am And That's All What I Yam (Popeye)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: Release hell WAS: [VOTE] Release Apache Commons Codec 1.5-RC1
Posted by sebb <se...@gmail.com>.
On 30 March 2011 19:23, Mark Thomas <ma...@apache.org> wrote:
> On 30/03/2011 18:43, Phil Steitz wrote:
>> I get that, which is why I think some kind of middle ground where we
>> provide simple scripts to move stuff around on the ASF hosts might
>> be a good compromise. This is essentially what the ibiblio-rysnch
>> stuff does. The only manual missing piece is correctly updating the
>> maven-metadata (which logically the assembly or other such plugin
>> could do locally) and maybe some kind of check to make sure that
>> things are deployed to the right directories.
>
> You might want to take a look at how Tomcat 7 does this. It is built
> with Ant [1] and has a separate Ant script [2] for uploading stuff to
> the ASF snapshot, staging and release repositories which also handles
> the meta-data.
But the script appears to need quite a lot of configuration that has
to match the release.
> Timing wise:
> - creating the release: 2 mins work + ~15 mins build time
> - uploading for voting: 2 mins work + ~60 mins transfer time
> - moving to dist if vote passes: 2 mins work
> - updating the site: 5 mins work
> - creating maven artifacts: 2 mins work + ~60 mins transfer time
>
> It constantly amazes me how much more complicated the release process
> appears to be in Commons for what should be much simpler components than
> Tomcat (no Windows installer, no native libraries, no fun with different
> NOTICE and LICENSE files for different jars, etc.).
However, Commons has a lot of different components with differing
numbers of release artifacts and diferent source directory layouts.
And at least one component does have native code (Daemon) and one has
special processing for user guide (Math) and another requires multiple
builds and jars (DBCP). And I think some may still use Maven 1.
I think a lot of the (perceived) complication is due to the fact that
the build instructions have not been fully updated since Maven 1.
Also, there are a lot of different RMs (generally one per component)
rather than one per Tomcat version, so the RMs are generally not as
familiar with the process.
If there is a problem with the Tomcat script, you can tweak it and
test it quite easily as there's only one product to test against.
Does the Tomcat 7 script work as is with Tomcat 6 and 5?
I'm not saying that the Commons release process could not be improved,
but I do think that:
- it is not as bad as people make out - though the docs need lots of work
- replacing it will not be a trivial task, because of the number of components
> I assume it shouldn't be too difficult to do a similar thing with a
> couple of Maven scripts.
Unfortunately Maven is much harder to tweak than Ant if one wants to
do anything slightly unusual, and debugging problems is much harder
than with Ant.
> Mark
>
> [1] http://svn.apache.org/viewvc/tomcat/trunk/build.xml?view=annotate
> [2]
> http://svn.apache.org/viewvc/tomcat/trunk/res/maven/mvn-pub.xml?view=annotate
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: Release hell WAS: [VOTE] Release Apache Commons Codec 1.5-RC1
Posted by Phil Steitz <ph...@gmail.com>.
On 3/30/11 11:23 AM, Mark Thomas wrote:
> On 30/03/2011 18:43, Phil Steitz wrote:
>> I get that, which is why I think some kind of middle ground where we
>> provide simple scripts to move stuff around on the ASF hosts might
>> be a good compromise. This is essentially what the ibiblio-rysnch
>> stuff does. The only manual missing piece is correctly updating the
>> maven-metadata (which logically the assembly or other such plugin
>> could do locally) and maybe some kind of check to make sure that
>> things are deployed to the right directories.
> You might want to take a look at how Tomcat 7 does this. It is built
> with Ant [1] and has a separate Ant script [2] for uploading stuff to
> the ASF snapshot, staging and release repositories which also handles
> the meta-data.
>
> Timing wise:
> - creating the release: 2 mins work + ~15 mins build time
> - uploading for voting: 2 mins work + ~60 mins transfer time
> - moving to dist if vote passes: 2 mins work
> - updating the site: 5 mins work
> - creating maven artifacts: 2 mins work + ~60 mins transfer time
>
> It constantly amazes me how much more complicated the release process
> appears to be in Commons for what should be much simpler components than
> Tomcat (no Windows installer, no native libraries, no fun with different
> NOTICE and LICENSE files for different jars, etc.).
>
> I assume it shouldn't be too difficult to do a similar thing with a
> couple of Maven scripts.
Thanks, Mark!
The mvn-pub script looks like it could be modified to do what we need.
I will see if I can get something like that working for the next
release I cut. The big advantage of that over my scripts and manual
moves on p.a.o is that it is platform independent and does not
require shell access for the maven deployment.
Phil
> Mark
>
> [1] http://svn.apache.org/viewvc/tomcat/trunk/build.xml?view=annotate
> [2]
> http://svn.apache.org/viewvc/tomcat/trunk/res/maven/mvn-pub.xml?view=annotate
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: Release hell WAS: [VOTE] Release Apache Commons Codec 1.5-RC1
Posted by Mark Thomas <ma...@apache.org>.
On 30/03/2011 18:43, Phil Steitz wrote:
> I get that, which is why I think some kind of middle ground where we
> provide simple scripts to move stuff around on the ASF hosts might
> be a good compromise. This is essentially what the ibiblio-rysnch
> stuff does. The only manual missing piece is correctly updating the
> maven-metadata (which logically the assembly or other such plugin
> could do locally) and maybe some kind of check to make sure that
> things are deployed to the right directories.
You might want to take a look at how Tomcat 7 does this. It is built
with Ant [1] and has a separate Ant script [2] for uploading stuff to
the ASF snapshot, staging and release repositories which also handles
the meta-data.
Timing wise:
- creating the release: 2 mins work + ~15 mins build time
- uploading for voting: 2 mins work + ~60 mins transfer time
- moving to dist if vote passes: 2 mins work
- updating the site: 5 mins work
- creating maven artifacts: 2 mins work + ~60 mins transfer time
It constantly amazes me how much more complicated the release process
appears to be in Commons for what should be much simpler components than
Tomcat (no Windows installer, no native libraries, no fun with different
NOTICE and LICENSE files for different jars, etc.).
I assume it shouldn't be too difficult to do a similar thing with a
couple of Maven scripts.
Mark
[1] http://svn.apache.org/viewvc/tomcat/trunk/build.xml?view=annotate
[2]
http://svn.apache.org/viewvc/tomcat/trunk/res/maven/mvn-pub.xml?view=annotate
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: Release hell WAS: [VOTE] Release Apache Commons Codec 1.5-RC1
Posted by Phil Steitz <ph...@gmail.com>.
On 3/30/11 10:24 AM, sebb wrote:
> On 30 March 2011 17:03, Phil Steitz <ph...@gmail.com> wrote:
>> On 3/30/11 5:39 AM, sebb wrote:
>>> On 30 March 2011 08:01, Luc Maisonobe <Lu...@free.fr> wrote:
>>>> Le 30/03/2011 03:36, Gary Gregory a écrit :
>>>>> 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.
>>>> For what its worth, for math 2.2 I used a mix of Phil scripts for the
>>>> beginning and Nexus for the rest, using the wiki as a guideline. In this
>>>> case the process was a little convoluted, because we create both a
>>>> trimmed down version of the site to hold only the user guide and to be
>>>> put in the docs archives, and we create a complete site to be uploaded.
>>>>
>>>> For the last release candidate, it worked well. Phil asked me to
>>>> document it and extend the scripts if needed, and I forgot to do it in
>>>> time, sorry :-(
>>>>
>>>> The one thing I found cumbersome was that part of the process pushed
>>>> non-maven artifacts on Nexus, that had to be manually moved away.
>>>> Furthermore, these are what we consider here the real Apache artifacts
>>>> (i.e. the ones that are available in the download page, not the ones
>>>> that are at last published in maven repository).
>>> I asked about extending Nexus so it could handle non-Maven staging,
>>> and that did seem to be possible, but whether it will ever be
>>> implemented, I don't know.
>>>
>>> That would be ideal.
>>>
>>>> I also have some slight concerns using a proprietary product, but as it
>>>> secures some things as Sebb says, I can live with it.
>>>>
>>>> Is it possible to find some intermediate approach, extending Phil
>>>> scripts, pushing only the maven part on Nexus directly without having to
>>>> log on Nexus web interface ? The last part (not logging to close the
>>>> staging area) may reduce the safety we get and risk some spurious
>>>> publish as Sebb explained, but with several independent scripts, this
>>>> could leverage the risk.
>>> Separating the deployments of Maven and non-Maven artifacts might be
>>> possible, but I'm not sure I have enough Maven-foo to do it.
>>>
>>> It would mean removing the non-maven stuff from deploy, and using some
>>> other means to copy the non-maven stuff to a separate staging
>>> directory.
>>>
>> There is this cool command called "cp" that works very well. There
> Does not work natively on Windows or various other OSes.
Last I checked, we do not run Windows on ASF infra at this point.
We are talking about moving stuff from ASF host to ASF host here.
For that, unix commands work just fine.
>> is another one called "tar" and even one called "scp" ;) If the
>> problem is that we want to be more paranoid than we are with the
>> mirrors for the maven stuff, why can't we just get access and copy
>> the files we want to put in the staging repo? Or write a simple
>> script that moves the kind of thing that I have sitting now in
>> http://people.apache.org/~psteitz/pool-1.5.6-rc2/maven/
>> to the "staging repository" and another script or command that
>> "promotes" it. It seems ridiculous to me that we need to introduce
>> a proprietary GUI tool to just move files on ASF hosts.
> Nexus does more than just move files around.
>
> It maintains the maven-metadata.xml file, and checks that the
> signature is correct.
> It also ensures that the file is uploaded to the correct directory
> based on the groupId.
> There are probably other features I have not encountered.
>
> If someone wants to spend time creating and maintaining an alternative
> tool, fine, but don't overlook the benefits that Nexus brings.
>
> At present I think it's great that I can do a "mvn deploy" and not
> worry that it might be published accidentally.
>
> Nexus makes it easy for non-Unix types to inspect the files and delete
> any that should not be there or upload others that are missing.
>
I get that, which is why I think some kind of middle ground where we
provide simple scripts to move stuff around on the ASF hosts might
be a good compromise. This is essentially what the ibiblio-rysnch
stuff does. The only manual missing piece is correctly updating the
maven-metadata (which logically the assembly or other such plugin
could do locally) and maybe some kind of check to make sure that
things are deployed to the right directories.
I like much better to be able to inspect the artifacts that I am
about to put out to vote locally. That is why I have never liked
"mvn deploy." I understand that others don't care so much about
that and are willing to trust maven to put what they think it is
going to deploy to where they think it is going to. With all the
layers of pom inheritance and history of bugs, I don't trust this
approach and it saves me no time personally. I also understand that
some Windows users may not want to mess with Cygwin or other tools
to provide scp and such, but I would prefer that at least this route
remain open to those of us who like to package and test locally and
deploy release artifacts manually.
Phil
>> Phil
>>
>> Phil
>>>> Luc
>>>>
>>>>> 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
>>>>>
>>>>> 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"?
>>>>>
>>>>> Or will that cause problem with work I did in Nexus (for the last time?)
>>>>>
>>>>> Thank you
>>>>>
>>>>> Gary
>>>>>
>>>>> ---------- Forwarded message ----------
>>>>> From: sebb <se...@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 <de...@commons.apache.org>
>>>>>
>>>>>
>>>>> On 29 March 2011 04:45, Gary Gregory <ga...@gmail.com> wrote:
>>>>>> On Mon, Mar 28, 2011 at 11:21 PM, Phil Steitz <ph...@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+F-@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 <garydgregory@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-unsubscribe@commons.apache.org
>>>>>>> For additional commands, e-mail: dev-help@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-unsubscribe@commons.apache.org
>>>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>>>
>>>>>
>>>>>
>>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>>
>>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>> For additional commands, e-mail: dev-help@commons.apache.org
>>
>>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: Release hell WAS: [VOTE] Release Apache Commons Codec 1.5-RC1
Posted by sebb <se...@gmail.com>.
On 30 March 2011 17:03, Phil Steitz <ph...@gmail.com> wrote:
> On 3/30/11 5:39 AM, sebb wrote:
>> On 30 March 2011 08:01, Luc Maisonobe <Lu...@free.fr> wrote:
>>> Le 30/03/2011 03:36, Gary Gregory a écrit :
>>>> 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.
>>> For what its worth, for math 2.2 I used a mix of Phil scripts for the
>>> beginning and Nexus for the rest, using the wiki as a guideline. In this
>>> case the process was a little convoluted, because we create both a
>>> trimmed down version of the site to hold only the user guide and to be
>>> put in the docs archives, and we create a complete site to be uploaded.
>>>
>>> For the last release candidate, it worked well. Phil asked me to
>>> document it and extend the scripts if needed, and I forgot to do it in
>>> time, sorry :-(
>>>
>>> The one thing I found cumbersome was that part of the process pushed
>>> non-maven artifacts on Nexus, that had to be manually moved away.
>>> Furthermore, these are what we consider here the real Apache artifacts
>>> (i.e. the ones that are available in the download page, not the ones
>>> that are at last published in maven repository).
>> I asked about extending Nexus so it could handle non-Maven staging,
>> and that did seem to be possible, but whether it will ever be
>> implemented, I don't know.
>>
>> That would be ideal.
>>
>>> I also have some slight concerns using a proprietary product, but as it
>>> secures some things as Sebb says, I can live with it.
>>>
>>> Is it possible to find some intermediate approach, extending Phil
>>> scripts, pushing only the maven part on Nexus directly without having to
>>> log on Nexus web interface ? The last part (not logging to close the
>>> staging area) may reduce the safety we get and risk some spurious
>>> publish as Sebb explained, but with several independent scripts, this
>>> could leverage the risk.
>> Separating the deployments of Maven and non-Maven artifacts might be
>> possible, but I'm not sure I have enough Maven-foo to do it.
>>
>> It would mean removing the non-maven stuff from deploy, and using some
>> other means to copy the non-maven stuff to a separate staging
>> directory.
>>
> There is this cool command called "cp" that works very well. There
Does not work natively on Windows or various other OSes.
> is another one called "tar" and even one called "scp" ;) If the
> problem is that we want to be more paranoid than we are with the
> mirrors for the maven stuff, why can't we just get access and copy
> the files we want to put in the staging repo? Or write a simple
> script that moves the kind of thing that I have sitting now in
> http://people.apache.org/~psteitz/pool-1.5.6-rc2/maven/
> to the "staging repository" and another script or command that
> "promotes" it. It seems ridiculous to me that we need to introduce
> a proprietary GUI tool to just move files on ASF hosts.
Nexus does more than just move files around.
It maintains the maven-metadata.xml file, and checks that the
signature is correct.
It also ensures that the file is uploaded to the correct directory
based on the groupId.
There are probably other features I have not encountered.
If someone wants to spend time creating and maintaining an alternative
tool, fine, but don't overlook the benefits that Nexus brings.
At present I think it's great that I can do a "mvn deploy" and not
worry that it might be published accidentally.
Nexus makes it easy for non-Unix types to inspect the files and delete
any that should not be there or upload others that are missing.
> Phil
>
> Phil
>>> Luc
>>>
>>>> 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
>>>>
>>>> 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"?
>>>>
>>>> Or will that cause problem with work I did in Nexus (for the last time?)
>>>>
>>>> Thank you
>>>>
>>>> Gary
>>>>
>>>> ---------- Forwarded message ----------
>>>> From: sebb <se...@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 <de...@commons.apache.org>
>>>>
>>>>
>>>> On 29 March 2011 04:45, Gary Gregory <ga...@gmail.com> wrote:
>>>>> On Mon, Mar 28, 2011 at 11:21 PM, Phil Steitz <ph...@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+F-@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 <garydgregory@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-unsubscribe@commons.apache.org
>>>>>> For additional commands, e-mail: dev-help@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-unsubscribe@commons.apache.org
>>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>>
>>>>
>>>>
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>
>>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>> For additional commands, e-mail: dev-help@commons.apache.org
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: Release hell WAS: [VOTE] Release Apache Commons Codec 1.5-RC1
Posted by Phil Steitz <ph...@gmail.com>.
On 3/30/11 5:39 AM, sebb wrote:
> On 30 March 2011 08:01, Luc Maisonobe <Lu...@free.fr> wrote:
>> Le 30/03/2011 03:36, Gary Gregory a écrit :
>>> 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.
>> For what its worth, for math 2.2 I used a mix of Phil scripts for the
>> beginning and Nexus for the rest, using the wiki as a guideline. In this
>> case the process was a little convoluted, because we create both a
>> trimmed down version of the site to hold only the user guide and to be
>> put in the docs archives, and we create a complete site to be uploaded.
>>
>> For the last release candidate, it worked well. Phil asked me to
>> document it and extend the scripts if needed, and I forgot to do it in
>> time, sorry :-(
>>
>> The one thing I found cumbersome was that part of the process pushed
>> non-maven artifacts on Nexus, that had to be manually moved away.
>> Furthermore, these are what we consider here the real Apache artifacts
>> (i.e. the ones that are available in the download page, not the ones
>> that are at last published in maven repository).
> I asked about extending Nexus so it could handle non-Maven staging,
> and that did seem to be possible, but whether it will ever be
> implemented, I don't know.
>
> That would be ideal.
>
>> I also have some slight concerns using a proprietary product, but as it
>> secures some things as Sebb says, I can live with it.
>>
>> Is it possible to find some intermediate approach, extending Phil
>> scripts, pushing only the maven part on Nexus directly without having to
>> log on Nexus web interface ? The last part (not logging to close the
>> staging area) may reduce the safety we get and risk some spurious
>> publish as Sebb explained, but with several independent scripts, this
>> could leverage the risk.
> Separating the deployments of Maven and non-Maven artifacts might be
> possible, but I'm not sure I have enough Maven-foo to do it.
>
> It would mean removing the non-maven stuff from deploy, and using some
> other means to copy the non-maven stuff to a separate staging
> directory.
>
There is this cool command called "cp" that works very well. There
is another one called "tar" and even one called "scp" ;) If the
problem is that we want to be more paranoid than we are with the
mirrors for the maven stuff, why can't we just get access and copy
the files we want to put in the staging repo? Or write a simple
script that moves the kind of thing that I have sitting now in
http://people.apache.org/~psteitz/pool-1.5.6-rc2/maven/
to the "staging repository" and another script or command that
"promotes" it. It seems ridiculous to me that we need to introduce
a proprietary GUI tool to just move files on ASF hosts.
Phil
Phil
>> Luc
>>
>>> 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
>>>
>>> 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"?
>>>
>>> Or will that cause problem with work I did in Nexus (for the last time?)
>>>
>>> Thank you
>>>
>>> Gary
>>>
>>> ---------- Forwarded message ----------
>>> From: sebb <se...@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 <de...@commons.apache.org>
>>>
>>>
>>> On 29 March 2011 04:45, Gary Gregory <ga...@gmail.com> wrote:
>>>> On Mon, Mar 28, 2011 at 11:21 PM, Phil Steitz <ph...@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+F-@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 <garydgregory@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-unsubscribe@commons.apache.org
>>>>> For additional commands, e-mail: dev-help@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-unsubscribe@commons.apache.org
>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>
>>>
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>> For additional commands, e-mail: dev-help@commons.apache.org
>>
>>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: Release hell WAS: [VOTE] Release Apache Commons Codec 1.5-RC1
Posted by sebb <se...@gmail.com>.
On 30 March 2011 08:01, Luc Maisonobe <Lu...@free.fr> wrote:
> Le 30/03/2011 03:36, Gary Gregory a écrit :
>> 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.
>
> For what its worth, for math 2.2 I used a mix of Phil scripts for the
> beginning and Nexus for the rest, using the wiki as a guideline. In this
> case the process was a little convoluted, because we create both a
> trimmed down version of the site to hold only the user guide and to be
> put in the docs archives, and we create a complete site to be uploaded.
>
> For the last release candidate, it worked well. Phil asked me to
> document it and extend the scripts if needed, and I forgot to do it in
> time, sorry :-(
>
> The one thing I found cumbersome was that part of the process pushed
> non-maven artifacts on Nexus, that had to be manually moved away.
> Furthermore, these are what we consider here the real Apache artifacts
> (i.e. the ones that are available in the download page, not the ones
> that are at last published in maven repository).
I asked about extending Nexus so it could handle non-Maven staging,
and that did seem to be possible, but whether it will ever be
implemented, I don't know.
That would be ideal.
> I also have some slight concerns using a proprietary product, but as it
> secures some things as Sebb says, I can live with it.
>
> Is it possible to find some intermediate approach, extending Phil
> scripts, pushing only the maven part on Nexus directly without having to
> log on Nexus web interface ? The last part (not logging to close the
> staging area) may reduce the safety we get and risk some spurious
> publish as Sebb explained, but with several independent scripts, this
> could leverage the risk.
Separating the deployments of Maven and non-Maven artifacts might be
possible, but I'm not sure I have enough Maven-foo to do it.
It would mean removing the non-maven stuff from deploy, and using some
other means to copy the non-maven stuff to a separate staging
directory.
> Luc
>
>>
>> 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
>>
>> 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"?
>>
>> Or will that cause problem with work I did in Nexus (for the last time?)
>>
>> Thank you
>>
>> Gary
>>
>> ---------- Forwarded message ----------
>> From: sebb <se...@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 <de...@commons.apache.org>
>>
>>
>> On 29 March 2011 04:45, Gary Gregory <ga...@gmail.com> wrote:
>>> On Mon, Mar 28, 2011 at 11:21 PM, Phil Steitz <ph...@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+F-@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 <garydgregory@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-unsubscribe@commons.apache.org
>>>> For additional commands, e-mail: dev-help@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-unsubscribe@commons.apache.org
>> For additional commands, e-mail: dev-help@commons.apache.org
>>
>>
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: Release hell WAS: [VOTE] Release Apache Commons Codec 1.5-RC1
Posted by Luc Maisonobe <Lu...@free.fr>.
Le 30/03/2011 03:36, Gary Gregory a écrit :
> 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.
For what its worth, for math 2.2 I used a mix of Phil scripts for the
beginning and Nexus for the rest, using the wiki as a guideline. In this
case the process was a little convoluted, because we create both a
trimmed down version of the site to hold only the user guide and to be
put in the docs archives, and we create a complete site to be uploaded.
For the last release candidate, it worked well. Phil asked me to
document it and extend the scripts if needed, and I forgot to do it in
time, sorry :-(
The one thing I found cumbersome was that part of the process pushed
non-maven artifacts on Nexus, that had to be manually moved away.
Furthermore, these are what we consider here the real Apache artifacts
(i.e. the ones that are available in the download page, not the ones
that are at last published in maven repository).
I also have some slight concerns using a proprietary product, but as it
secures some things as Sebb says, I can live with it.
Is it possible to find some intermediate approach, extending Phil
scripts, pushing only the maven part on Nexus directly without having to
log on Nexus web interface ? The last part (not logging to close the
staging area) may reduce the safety we get and risk some spurious
publish as Sebb explained, but with several independent scripts, this
could leverage the risk.
Luc
>
> 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
>
> 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"?
>
> Or will that cause problem with work I did in Nexus (for the last time?)
>
> Thank you
>
> Gary
>
> ---------- Forwarded message ----------
> From: sebb <se...@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 <de...@commons.apache.org>
>
>
> On 29 March 2011 04:45, Gary Gregory <ga...@gmail.com> wrote:
>> On Mon, Mar 28, 2011 at 11:21 PM, Phil Steitz <ph...@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+F-@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 <garydgregory@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-unsubscribe@commons.apache.org
>>> For additional commands, e-mail: dev-help@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-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: Release hell WAS: [VOTE] Release Apache Commons Codec 1.5-RC1
Posted by Ted Dunning <te...@gmail.com>.
That wasn't maven. That was a sloppy eclipse "create project"
implementation.
On Tue, Mar 29, 2011 at 7:24 PM, Stephen Williams <sd...@lig.net> wrote:
> So, lesson learned: Don't use Maven! ;-)
> No, the other one: make copies of your code through multiple means until it
> is completely safe. I hadn't lost code (or any data through paranoid
> backups that have survived about 20 hard drive failures over the years) for
> a long time. It will be a very long time before it happens again.
>
Re: Release hell WAS: [VOTE] Release Apache Commons Codec 1.5-RC1
Posted by Stephen Williams <sd...@lig.net>.
On 3/30/11 12:02 AM, Ralph Goers wrote:
> On Mar 29, 2011, at 7:40 PM, Stephen Williams wrote:
>> On 3/29/11 7:33 PM, Ralph Goers wrote:
>>> On Mar 29, 2011, at 7:24 PM, Stephen Williams wrote:
>>>> ...
>>>> So, lesson learned: Don't use Maven! ;-)
>>>> No, the other one: make copies of your code through multiple means until it is completely safe. I hadn't lost code (or any data through paranoid backups that have survived about 20 hard drive failures over the years) for a long time. It will be a very long time before it happens again.
>>>>
>>> I have no idea what you did, but Maven won't delete your source code doing a mvn clean install unless you've placed your source files under the "target" subdirectory. This could have just as easily been something Eclipse did to you as much as Maven. Maybe you should stop using Eclipse then.
>> It was under 'src' at the project top... Using Eclipse, without Maven, before and after has always worked fine. I've never seen Eclipse delete source files automatically ever, other than when triggering that Maven build.
>> Probably it was some obscure thing about the already-existing Maven environment or something. I couldn't explain it and didn't have extra time or energy to debug or duplicate. But that's what happened.
> I don't doubt that it happened. I just doubt it was caused by Maven itself. I know of no operation that will delete the src directory or anything under it. While you are perfectly free to decide to not use Maven, basing the decision solely on the experience you related is not rational. The choice almost always comes down to Maven being "inflexible" (i.e. requiring
It was rational given my evidence so far. Just not given your evidence. I'll chalk it up to an unlucky combination of beginner
steps. I'm likely to dig into it again soon.
> you to do things its way) vs having hand coded builds with little consistency from project to project.
I don't mind the consistency, however I am not happy when things are more complicated than they need to be. I see the advantage of
Maven for automatically providing apt/yum/CPAN-like package management for Java. I'm just not sure it is the simplest way to do it
or that it is something I'd choose for my own project code.
> Ralph
>
sdw
Re: Release hell WAS: [VOTE] Release Apache Commons Codec 1.5-RC1
Posted by Ralph Goers <ra...@dslextreme.com>.
On Mar 29, 2011, at 7:40 PM, Stephen Williams wrote:
> On 3/29/11 7:33 PM, Ralph Goers wrote:
>> On Mar 29, 2011, at 7:24 PM, Stephen Williams wrote:
>>> ...
>>> So, lesson learned: Don't use Maven! ;-)
>>> No, the other one: make copies of your code through multiple means until it is completely safe. I hadn't lost code (or any data through paranoid backups that have survived about 20 hard drive failures over the years) for a long time. It will be a very long time before it happens again.
>>>
>> I have no idea what you did, but Maven won't delete your source code doing a mvn clean install unless you've placed your source files under the "target" subdirectory. This could have just as easily been something Eclipse did to you as much as Maven. Maybe you should stop using Eclipse then.
>
> It was under 'src' at the project top... Using Eclipse, without Maven, before and after has always worked fine. I've never seen Eclipse delete source files automatically ever, other than when triggering that Maven build.
> Probably it was some obscure thing about the already-existing Maven environment or something. I couldn't explain it and didn't have extra time or energy to debug or duplicate. But that's what happened.
I don't doubt that it happened. I just doubt it was caused by Maven itself. I know of no operation that will delete the src directory or anything under it. While you are perfectly free to decide to not use Maven, basing the decision solely on the experience you related is not rational. The choice almost always comes down to Maven being "inflexible" (i.e. requiring you to do things its way) vs having hand coded builds with little consistency from project to project.
Ralph
Re: Release hell WAS: [VOTE] Release Apache Commons Codec 1.5-RC1
Posted by Stephen Williams <sd...@lig.net>.
On 3/29/11 7:33 PM, Ralph Goers wrote:
> On Mar 29, 2011, at 7:24 PM, Stephen Williams wrote:
>> ...
>> So, lesson learned: Don't use Maven! ;-)
>> No, the other one: make copies of your code through multiple means until it is completely safe. I hadn't lost code (or any data through paranoid backups that have survived about 20 hard drive failures over the years) for a long time. It will be a very long time before it happens again.
>>
> I have no idea what you did, but Maven won't delete your source code doing a mvn clean install unless you've placed your source files under the "target" subdirectory. This could have just as easily been something Eclipse did to you as much as Maven. Maybe you should stop using Eclipse then.
It was under 'src' at the project top... Using Eclipse, without Maven, before and after has always worked fine. I've never seen
Eclipse delete source files automatically ever, other than when triggering that Maven build.
Probably it was some obscure thing about the already-existing Maven environment or something. I couldn't explain it and didn't have
extra time or energy to debug or duplicate. But that's what happened.
> Ralph
sdw
Re: Release hell WAS: [VOTE] Release Apache Commons Codec 1.5-RC1
Posted by Ralph Goers <ra...@dslextreme.com>.
On Mar 29, 2011, at 7:24 PM, Stephen Williams wrote:
> On 3/29/11 6:36 PM, Gary Gregory wrote:
>> Wait! I'm not done or I'm loosing my marbles...
>
> ...
> As I noticed this note, seems like a good point to interject a Maven war story:
>
> I do not like Maven. I know I should, but it seems too complicated and too hard to use on complex projects. I may get over it, when I have a good reason. I'm living in CMake land now, compiling C++ and Java code, and (using JavaGlue (a fork of XBiG)) generating, compiling, and linking Java->C++ code for native and Android apps. It seems much cleaner, handles cross-platform very well, and it is easier to avoid ant/gmake/maven spaghetti code. Not as powerful as Maven probably, but easier for most project use.
>
> A bit over a year ago I was on a project that had way too much code (class diarrhea (600+ for a 3 tier application) etc.) written by a Russian off-shore team. They had a long-running and memory hog (6+GB!) Maven build. At runtime, various OSGi bits were used to tie the application together, mainly meaning that it was impossible to follow the whole flow to figure out how certain parts of the app were triggered. And there was no detailed documentation and they refused to refactor.
>
> Anyway, at one point I'd written a good chunk of code using Google Protocol buffers in a message-oriented way (the code assumes synchronous RPC) using the nice Apache Netty framework. Plus we used RabbitMQ on another tier. Grudgingly following the (wrong!) project rule of not checking in things until they were working, I finished a complete version. After testing, I decided to dig into integrating the build of that module into Maven. Noticing that Eclipse had a 'create Maven project file' (or something like that), I figured I'd give it a try. Assuming that build errors would lead me to the next step, I asked Eclipse for a project build.
>
> Every buffer my mouse ran over in Eclipse blanked. What? Wait! Arghh... The first thing the generated Maven build did was to delete all of my source code. I've used a lot of build systems for a lot of years, but didn't anticipate that possibility. I checked all tmp, cache, and other areas. No trace of any source code.
>
> So, in shock and not happy for half a day, kicking myself for not making copies in a dozen places, I started being resigned to writing the code from scratch. Probably I would remember most of the difficult solutions.
>
> Then, I noticed that the class files were still there. (Delete the source code but not the class files? Perverted!) For about a day, I tried all of the Java decompilers that I could find. Most of them couldn't handle JDK1.5 class files. Finally, one worked almost perfectly and I recovered over 98% of my code. No comments of course, and its a good thing we weren't obfuscating at that point.
>
> So, lesson learned: Don't use Maven! ;-)
> No, the other one: make copies of your code through multiple means until it is completely safe. I hadn't lost code (or any data through paranoid backups that have survived about 20 hard drive failures over the years) for a long time. It will be a very long time before it happens again.
>
> sdw
> --
> Stephen D. Williams sdw@lig.net stephendwilliams@gmail.com LinkedIn: http://sdw.st/in V:650-450-UNIX (8649) V:866.SDW.UNIX V:703.371.9362 F:703.995.0407 AIM:sdw Skype:StephenDWilliams Yahoo:sdwlignet Resume: http://sdw.st/gres Personal: http://sdw.st facebook.com/sdwlig twitter.com/scienteer
I have no idea what you did, but Maven won't delete your source code doing a mvn clean install unless you've placed your source files under the "target" subdirectory. This could have just as easily been something Eclipse did to you as much as Maven. Maybe you should stop using Eclipse then.
Ralph
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: Release hell WAS: [VOTE] Release Apache Commons Codec 1.5-RC1
Posted by Stephen Williams <sd...@lig.net>.
On 3/29/11 6:36 PM, Gary Gregory wrote:
> Wait! I'm not done or I'm loosing my marbles...
...
As I noticed this note, seems like a good point to interject a Maven war story:
I do not like Maven. I know I should, but it seems too complicated and too hard to use on complex projects. I may get over it,
when I have a good reason. I'm living in CMake land now, compiling C++ and Java code, and (using JavaGlue (a fork of XBiG))
generating, compiling, and linking Java->C++ code for native and Android apps. It seems much cleaner, handles cross-platform very
well, and it is easier to avoid ant/gmake/maven spaghetti code. Not as powerful as Maven probably, but easier for most project use.
A bit over a year ago I was on a project that had way too much code (class diarrhea (600+ for a 3 tier application) etc.) written by
a Russian off-shore team. They had a long-running and memory hog (6+GB!) Maven build. At runtime, various OSGi bits were used to
tie the application together, mainly meaning that it was impossible to follow the whole flow to figure out how certain parts of the
app were triggered. And there was no detailed documentation and they refused to refactor.
Anyway, at one point I'd written a good chunk of code using Google Protocol buffers in a message-oriented way (the code assumes
synchronous RPC) using the nice Apache Netty framework. Plus we used RabbitMQ on another tier. Grudgingly following the (wrong!)
project rule of not checking in things until they were working, I finished a complete version. After testing, I decided to dig into
integrating the build of that module into Maven. Noticing that Eclipse had a 'create Maven project file' (or something like that),
I figured I'd give it a try. Assuming that build errors would lead me to the next step, I asked Eclipse for a project build.
Every buffer my mouse ran over in Eclipse blanked. What? Wait! Arghh... The first thing the generated Maven build did was to
delete all of my source code. I've used a lot of build systems for a lot of years, but didn't anticipate that possibility. I
checked all tmp, cache, and other areas. No trace of any source code.
So, in shock and not happy for half a day, kicking myself for not making copies in a dozen places, I started being resigned to
writing the code from scratch. Probably I would remember most of the difficult solutions.
Then, I noticed that the class files were still there. (Delete the source code but not the class files? Perverted!) For about a
day, I tried all of the Java decompilers that I could find. Most of them couldn't handle JDK1.5 class files. Finally, one worked
almost perfectly and I recovered over 98% of my code. No comments of course, and its a good thing we weren't obfuscating at that point.
So, lesson learned: Don't use Maven! ;-)
No, the other one: make copies of your code through multiple means until it is completely safe. I hadn't lost code (or any data
through paranoid backups that have survived about 20 hard drive failures over the years) for a long time. It will be a very long
time before it happens again.
sdw
--
Stephen D. Williams sdw@lig.net stephendwilliams@gmail.com LinkedIn: http://sdw.st/in V:650-450-UNIX (8649) V:866.SDW.UNIX
V:703.371.9362 F:703.995.0407 AIM:sdw Skype:StephenDWilliams Yahoo:sdwlignet Resume: http://sdw.st/gres Personal: http://sdw.st
facebook.com/sdwlig twitter.com/scienteer
Re: Release hell WAS: [VOTE] Release Apache Commons Codec 1.5-RC1
Posted by Gary Gregory <ga...@gmail.com>.
On Tue, Mar 29, 2011 at 10:24 PM, sebb <se...@gmail.com> wrote:
> 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.
>
Thanks for checking.
Gary
> On 30 March 2011 02:58, Gary Gregory <ga...@gmail.com> wrote:
> > On Tue, Mar 29, 2011 at 9:52 PM, sebb <se...@gmail.com> wrote:
> >>
> >> On 30 March 2011 02:36, Gary Gregory <ga...@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 <se...@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 <de...@commons.apache.org>
> >> >
> >> >
> >> > On 29 March 2011 04:45, Gary Gregory <ga...@gmail.com> wrote:
> >> >> On Mon, Mar 28, 2011 at 11:21 PM, Phil Steitz <phil.steitz@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+F-@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
> >> >>> > <garydgregory@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-unsubscribe@commons.apache.org
> >> >>> For additional commands, e-mail: dev-help@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-unsubscribe@commons.apache.org
> >> > For additional commands, e-mail: dev-help@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-unsubscribe@commons.apache.org
> >> For additional commands, e-mail: dev-help@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-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
--
Thank you,
Gary
http://garygregory.wordpress.com/
http://garygregory.com/
http://people.apache.org/~ggregory/
http://twitter.com/GaryGregory
Re: Release hell WAS: [VOTE] Release Apache Commons Codec 1.5-RC1
Posted by sebb <se...@gmail.com>.
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 <ga...@gmail.com> wrote:
> On Tue, Mar 29, 2011 at 9:52 PM, sebb <se...@gmail.com> wrote:
>>
>> On 30 March 2011 02:36, Gary Gregory <ga...@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 <se...@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 <de...@commons.apache.org>
>> >
>> >
>> > On 29 March 2011 04:45, Gary Gregory <ga...@gmail.com> wrote:
>> >> On Mon, Mar 28, 2011 at 11:21 PM, Phil Steitz <ph...@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+F-@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
>> >>> > <garydgregory@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-unsubscribe@commons.apache.org
>> >>> For additional commands, e-mail: dev-help@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-unsubscribe@commons.apache.org
>> > For additional commands, e-mail: dev-help@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-unsubscribe@commons.apache.org
>> For additional commands, e-mail: dev-help@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-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: Release hell WAS: [VOTE] Release Apache Commons Codec 1.5-RC1
Posted by Gary Gregory <ga...@gmail.com>.
On Tue, Mar 29, 2011 at 9:52 PM, sebb <se...@gmail.com> wrote:
> On 30 March 2011 02:36, Gary Gregory <ga...@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 <se...@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 <de...@commons.apache.org>
> >
> >
> > On 29 March 2011 04:45, Gary Gregory <ga...@gmail.com> wrote:
> >> On Mon, Mar 28, 2011 at 11:21 PM, Phil Steitz <ph...@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+F-@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 <
> garydgregory@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-unsubscribe@commons.apache.org
> >>> For additional commands, e-mail: dev-help@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-unsubscribe@commons.apache.org
> > For additional commands, e-mail: dev-help@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-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
--
Thank you,
Gary
http://garygregory.wordpress.com/
http://garygregory.com/
http://people.apache.org/~ggregory/
http://twitter.com/GaryGregory
Re: Release hell WAS: [VOTE] Release Apache Commons Codec 1.5-RC1
Posted by sebb <se...@gmail.com>.
On 30 March 2011 02:36, Gary Gregory <ga...@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.
> Thank you
>
> Gary
>
> ---------- Forwarded message ----------
> From: sebb <se...@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 <de...@commons.apache.org>
>
>
> On 29 March 2011 04:45, Gary Gregory <ga...@gmail.com> wrote:
>> On Mon, Mar 28, 2011 at 11:21 PM, Phil Steitz <ph...@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+F-@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 <garydgregory@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-unsubscribe@commons.apache.org
>>> For additional commands, e-mail: dev-help@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-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@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-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org