You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ant.apache.org by Charles Duffy <ch...@dyfis.net> on 2014/01/20 19:19:38 UTC
[VOTE] Ivy 2.4.0-rc1 Release
I have built a release candidate for Ivy 2.4.0.
You can download it from this URL:
http://people.apache.org/~cduffy/ivy-2.4.0-rc1/
Do you vote for the release of these binaries?
[ ] Yes
[ ] No
Regards,
Charles Duffy, Ivy 2.4.0 release manager
PS -- As this build was performed on hardware owned by Indeed, Inc., the
binaries are signed with the duffy@indeed.com GPG key. For any final
release, I would be using hardware under personal control and a key
associated with cduffy@apache.org.
Re: [VOTE] Ivy 2.4.0-rc1 Release
Posted by Antoine Levy Lambert <an...@gmx.de>.
Charles,
Thanks for creating a release so fast.
Where is your public GPG key ? Should it get added to http://svn.apache.org/repos/asf/ant/core/trunk/KEYS so that people can check the .asc files in the release candidate. Or is it available elsewhere ?
+1 for the release
Antoine
On Jan 20, 2014, at 1:19 PM, Charles Duffy wrote:
> I have built a release candidate for Ivy 2.4.0.
>
> You can download it from this URL:
> http://people.apache.org/~cduffy/ivy-2.4.0-rc1/
>
> Do you vote for the release of these binaries?
>
> [ ] Yes
> [ ] No
>
> Regards,
>
> Charles Duffy, Ivy 2.4.0 release manager
>
>
> PS -- As this build was performed on hardware owned by Indeed, Inc., the
> binaries are signed with the duffy@indeed.com GPG key. For any final
> release, I would be using hardware under personal control and a key
> associated with cduffy@apache.org.
Re: [VOTE] Ivy 2.4.0-rc1 Release
Posted by Antoine Levy Lambert <an...@gmx.de>.
Hello Maarten,
thanks for volunteering. Maybe I will will volunteer for the next one.
Regards,
Antoine
On Mar 10, 2014, at 6:19 PM, Maarten Coene <ma...@yahoo.com> wrote:
> No problem Charles,
> I can finish the release for you unless there are other candidates who want to give it a try?
>
> thanks,
> Maarten
>
>
>
>
> ________________________________
> Van: Charles Duffy <ch...@dyfis.net>
> Aan: Ant Developers List <de...@ant.apache.org>
> Verzonden: maandag 10 maart 16:47 2014
> Onderwerp: Re: [VOTE] Ivy 2.4.0-rc1 Release
>
>
> If you could finish up, that would be very much appreciated. Whereas my
> former employer allowed for some amount of Ivy work on business hours, such
> is no longer the case, and my personal time has more demands than I'm
> presently able to satisfy.
>
> Thank you kindly, and please accept my apologies.
>
>
>
> On Tue, Mar 4, 2014 at 8:46 PM, Antoine Levy Lambert <an...@gmx.de> wrote:
>
>> Charles,
>>
>> are you going to be able to finish the release ?
>>
>> Do you need some help ?
>>
>> Best regards,
>>
>> Antoine
>> On Feb 25, 2014, at 8:18 AM, Antoine Levy Lambert <an...@gmx.de> wrote:
>>
>>> Hi,
>>>
>>> I still do not see the public GPG key of Charles under
>> https://dist.apache.org/repos/dist/release/ant/KEYS
>>>
>>> I did the following checkout to create a small sandbox with this KEYS
>> file in it :
>>>
>>>
>>>
>>> svn checkout --depth=files --depth=files
>> https://dist.apache.org/repos/dist/release/ant/ dist-release-ant
>>>
>>> Charles, let us know if you can check in your public key there.
>>>
>>>
>>>
>>> Antoine
>>>
>>>
>>>
>>> On Feb 15, 2014, at 9:23 AM, Nicolas Lalevée <ni...@hibnet.org>
>> wrote:
>>>
>>>> Note that the release if not accepted yet, it cannot be published.
>>>>
>>>> Nicolas
>>>>
>>>> Le 14 févr. 2014 à 14:55, Charles Duffy <ch...@dyfis.net> a écrit :
>>>>
>>>>> Apologies -- new job; I dropped the ball somewhat. I'll try to get
>> things
>>>>> back on track this weekend.
>>>>>
>>>>>
>>>>> On Fri, Feb 14, 2014 at 1:58 AM, Jean-Louis Boudart <
>>>>> jeanlouis.boudart@gmail.com> wrote:
>>>>>
>>>>>> Is the release over ?
>>>>>>
>>>>>> I dont find it on maven central
>>>>>> Le 28 janv. 2014 01:46, "Charles Duffy" <ch...@dyfis.net> a écrit :
>>>>>>
>>>>>>> The keys are actually different -- the one used by the
>> currently-posted
>>>>>>> .asc files is associated with Indeed, Inc. I'll be resigning the
>> binaries
>>>>>>> after verifying that their Indeed signatures are intact (and moving
>> them
>>>>>> to
>>>>>>> dist.apache.org at that time).
>>>>>>>
>>>>>>> Expect a note in this thread when that happens.
>>>>>>>
>>>>>>>
>>>>>>> On Mon, Jan 27, 2014 at 6:42 PM, Nicolas Lalevée <
>>>>>>> nicolas.lalevee@hibnet.org
>>>>>>>> wrote:
>>>>>>>
>>>>>>>>
>>>>>>>> Le 22 janv. 2014 à 00:52, Nicolas Lalevée <
>> nicolas.lalevee@hibnet.org>
>>>>>> a
>>>>>>>> écrit :
>>>>>>>>
>>>>>>>>> I have found some issues. The source distribution seems to miss
>> some
>>>>>>>> test files. I guess this has been the case for quite some time. And
>> it
>>>>>> is
>>>>>>>> "just" about the tests. And it is an RC. So OK for me. And I will
>> fix
>>>>>>> that
>>>>>>>> soon in trunk.
>>>>>>>>>
>>>>>>>>> To avoid confusion and make things simpler, I suggest we modify the
>>>>>>>> release process to that everything goes through the svn of
>>>>>>> dist.apache.org,
>>>>>>>> and not use anymore people.apache.org. In the end, everything is
>>>>>>>> published there.
>>>>>>>>> And I'll modify in the doc of the release process the template of
>> the
>>>>>>>> email of the vote to include a line that is referencing the svn
>> tag. So
>>>>>>>> it's more difficult to miss it, and it is helpful to do review.
>>>>>>>>>
>>>>>>>>> I have tested the staging update site: works like a charm.
>>>>>>>>>
>>>>>>>>> So LGTM.
>>>>>>>>>
>>>>>>>>> I will cast my vote as soon as I can verify the signature of the
>>>>>>>> artifacts.
>>>>>>>>
>>>>>>>> You pushed some keys to the KEYS files, but it doesn't seems to be
>> the
>>>>>>>> same as the one you used to sign the proposed artifacts.
>>>>>>>>
>>>>>>>> My gpg is asking for the key ID 93FB868A. Did I do something wrong
>> or
>>>>>> the
>>>>>>>> keys are actually different ?
>>>>>>>>
>>>>>>>> Nicolas
>>>>>>>>
>>>>>>>>
>>>>>>>>>
>>>>>>>>> Nicolas
>>>>>>>>>
>>>>>>>>> Le 21 janv. 2014 à 17:19, Charles Duffy <ch...@dyfis.net> a
>> écrit
>>>>>> :
>>>>>>>>>
>>>>>>>>>> FYI --
>>>>>>>>>>
>>>>>>>>>> A tag at
>>>>>>> https://svn.apache.org/repos/asf/ant/ivy/core/tags/2.4.0-rc1now
>>>>>>>>>> exists. This differs from the branch head from which the binaries
>>>>>> for
>>>>>>>> test
>>>>>>>>>> were built only inasmuch as its svn:externals specify a specific
>>>>>>>> revision
>>>>>>>>>> of the documentation build tools rather than leaving their
>> revision
>>>>>>>>>> floating.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Tue, Jan 21, 2014 at 6:54 AM, Charles Duffy <charles@dyfis.net
>>>
>>>>>>>> wrote:
>>>>>>>>>>
>>>>>>>>>>> Howdy --
>>>>>>>>>>>
>>>>>>>>>>> I've attempted to follow the documentation at
>>>>>>>>>>> http://ant.apache.org/ivy/history/trunk/dev/makerelease.html and
>>>>>>>>>>>
>>>>>> http://ant.apache.org/ivy/ivyde/history/trunk/dev/updatesite.html(as
>>>>>>>>>>> included-by-reference in the former) in preparing the above. That
>>>>>>>> said, it
>>>>>>>>>>> appears that I missed step 12 (and, accordingly, have a 1.4.0-rc1
>>>>>>>> branch,
>>>>>>>>>>> from the present tip of which the binaries were built, but no
>>>>>>>> associated
>>>>>>>>>>> tag).
>>>>>>>>>>>
>>>>>>>>>>> I'll be sure to get KEYS up-to-date. Thank you for the pointers.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On Tue, Jan 21, 2014 at 6:26 AM, Stefan Bodewig <
>>>>>> bodewig@apache.org
>>>>>>>>> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> Hi Charles,
>>>>>>>>>>>>
>>>>>>>>>>>> we don't really release binaries, they are just a convenience.
>>>>>> All
>>>>>>>> that
>>>>>>>>>>>> matters as a release is the sources.
>>>>>>>>>>>>
>>>>>>>>>>>> I'm not sure there is anything documenting the release process
>> for
>>>>>>> Ivy
>>>>>>>>>>>> but in general you create an svn tag and build source and binary
>>>>>>>>>>>> distributions from that.
>>>>>>>>>>>>
>>>>>>>>>>>> What you have built now is a binary for testing and you don't
>>>>>> really
>>>>>>>>>>>> need to vote on that at all. Just encourage people to try it
>> out
>>>>>>> :-)
>>>>>>>>>>>>
>>>>>>>>>>>> If you want to perform some sort of test-release, have a look at
>>>>>>>>>>>> <
>> http://svn.apache.org/repos/asf/ant/antlibs/ReleaseInstructions>
>>>>>>> and
>>>>>>>>>>>> similar instructions to get an idea of what is expected.
>>>>>>>>>>>>
>>>>>>>>>>>>> PS -- As this build was performed on hardware owned by Indeed,
>>>>>>> Inc.,
>>>>>>>> the
>>>>>>>>>>>>> binaries are signed with the duffy@indeed.com GPG key. For any
>>>>>>> final
>>>>>>>>>>>>> release, I would be using hardware under personal control and a
>>>>>> key
>>>>>>>>>>>>> associated with cduffy@apache.org.
>>>>>>>>>>>>
>>>>>>>>>>>> Please make sure whatever key you use is inside
>>>>>>>>>>>> https://dist.apache.org/repos/dist/release/ant/KEYS - if you
>> need
>>>>>>> any
>>>>>>>>>>>> help committing it there, please yell.
>>>>>>>>>>>>
>>>>>>>>>>>> Cheers
>>>>>>>>>>>>
>>>>>>>>>>>> Stefan
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>> ---------------------------------------------------------------------
>>>>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
>>>>>>>>>>>> For additional commands, e-mail: dev-help@ant.apache.org
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>> ---------------------------------------------------------------------
>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
>>>>>>>>> For additional commands, e-mail: dev-help@ant.apache.org
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>> ---------------------------------------------------------------------
>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
>>>>>>>> For additional commands, e-mail: dev-help@ant.apache.org
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
>>>> For additional commands, e-mail: dev-help@ant.apache.org
>>>>
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
>> For additional commands, e-mail: dev-help@ant.apache.org
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org
Re: [VOTE] Ivy 2.4.0-rc1 Release
Posted by Maarten Coene <ma...@yahoo.com>.
No problem Charles,
I can finish the release for you unless there are other candidates who want to give it a try?
thanks,
Maarten
________________________________
Van: Charles Duffy <ch...@dyfis.net>
Aan: Ant Developers List <de...@ant.apache.org>
Verzonden: maandag 10 maart 16:47 2014
Onderwerp: Re: [VOTE] Ivy 2.4.0-rc1 Release
If you could finish up, that would be very much appreciated. Whereas my
former employer allowed for some amount of Ivy work on business hours, such
is no longer the case, and my personal time has more demands than I'm
presently able to satisfy.
Thank you kindly, and please accept my apologies.
On Tue, Mar 4, 2014 at 8:46 PM, Antoine Levy Lambert <an...@gmx.de> wrote:
> Charles,
>
> are you going to be able to finish the release ?
>
> Do you need some help ?
>
> Best regards,
>
> Antoine
> On Feb 25, 2014, at 8:18 AM, Antoine Levy Lambert <an...@gmx.de> wrote:
>
> > Hi,
> >
> > I still do not see the public GPG key of Charles under
> https://dist.apache.org/repos/dist/release/ant/KEYS
> >
> > I did the following checkout to create a small sandbox with this KEYS
> file in it :
> >
> >
> >
> > svn checkout --depth=files --depth=files
> https://dist.apache.org/repos/dist/release/ant/ dist-release-ant
> >
> > Charles, let us know if you can check in your public key there.
> >
> >
> >
> > Antoine
> >
> >
> >
> > On Feb 15, 2014, at 9:23 AM, Nicolas Lalevée <ni...@hibnet.org>
> wrote:
> >
> >> Note that the release if not accepted yet, it cannot be published.
> >>
> >> Nicolas
> >>
> >> Le 14 févr. 2014 à 14:55, Charles Duffy <ch...@dyfis.net> a écrit :
> >>
> >>> Apologies -- new job; I dropped the ball somewhat. I'll try to get
> things
> >>> back on track this weekend.
> >>>
> >>>
> >>> On Fri, Feb 14, 2014 at 1:58 AM, Jean-Louis Boudart <
> >>> jeanlouis.boudart@gmail.com> wrote:
> >>>
> >>>> Is the release over ?
> >>>>
> >>>> I dont find it on maven central
> >>>> Le 28 janv. 2014 01:46, "Charles Duffy" <ch...@dyfis.net> a écrit :
> >>>>
> >>>>> The keys are actually different -- the one used by the
> currently-posted
> >>>>> .asc files is associated with Indeed, Inc. I'll be resigning the
> binaries
> >>>>> after verifying that their Indeed signatures are intact (and moving
> them
> >>>> to
> >>>>> dist.apache.org at that time).
> >>>>>
> >>>>> Expect a note in this thread when that happens.
> >>>>>
> >>>>>
> >>>>> On Mon, Jan 27, 2014 at 6:42 PM, Nicolas Lalevée <
> >>>>> nicolas.lalevee@hibnet.org
> >>>>>> wrote:
> >>>>>
> >>>>>>
> >>>>>> Le 22 janv. 2014 à 00:52, Nicolas Lalevée <
> nicolas.lalevee@hibnet.org>
> >>>> a
> >>>>>> écrit :
> >>>>>>
> >>>>>>> I have found some issues. The source distribution seems to miss
> some
> >>>>>> test files. I guess this has been the case for quite some time. And
> it
> >>>> is
> >>>>>> "just" about the tests. And it is an RC. So OK for me. And I will
> fix
> >>>>> that
> >>>>>> soon in trunk.
> >>>>>>>
> >>>>>>> To avoid confusion and make things simpler, I suggest we modify the
> >>>>>> release process to that everything goes through the svn of
> >>>>> dist.apache.org,
> >>>>>> and not use anymore people.apache.org. In the end, everything is
> >>>>>> published there.
> >>>>>>> And I'll modify in the doc of the release process the template of
> the
> >>>>>> email of the vote to include a line that is referencing the svn
> tag. So
> >>>>>> it's more difficult to miss it, and it is helpful to do review.
> >>>>>>>
> >>>>>>> I have tested the staging update site: works like a charm.
> >>>>>>>
> >>>>>>> So LGTM.
> >>>>>>>
> >>>>>>> I will cast my vote as soon as I can verify the signature of the
> >>>>>> artifacts.
> >>>>>>
> >>>>>> You pushed some keys to the KEYS files, but it doesn't seems to be
> the
> >>>>>> same as the one you used to sign the proposed artifacts.
> >>>>>>
> >>>>>> My gpg is asking for the key ID 93FB868A. Did I do something wrong
> or
> >>>> the
> >>>>>> keys are actually different ?
> >>>>>>
> >>>>>> Nicolas
> >>>>>>
> >>>>>>
> >>>>>>>
> >>>>>>> Nicolas
> >>>>>>>
> >>>>>>> Le 21 janv. 2014 à 17:19, Charles Duffy <ch...@dyfis.net> a
> écrit
> >>>> :
> >>>>>>>
> >>>>>>>> FYI --
> >>>>>>>>
> >>>>>>>> A tag at
> >>>>> https://svn.apache.org/repos/asf/ant/ivy/core/tags/2.4.0-rc1now
> >>>>>>>> exists. This differs from the branch head from which the binaries
> >>>> for
> >>>>>> test
> >>>>>>>> were built only inasmuch as its svn:externals specify a specific
> >>>>>> revision
> >>>>>>>> of the documentation build tools rather than leaving their
> revision
> >>>>>>>> floating.
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> On Tue, Jan 21, 2014 at 6:54 AM, Charles Duffy <charles@dyfis.net
> >
> >>>>>> wrote:
> >>>>>>>>
> >>>>>>>>> Howdy --
> >>>>>>>>>
> >>>>>>>>> I've attempted to follow the documentation at
> >>>>>>>>> http://ant.apache.org/ivy/history/trunk/dev/makerelease.html and
> >>>>>>>>>
> >>>> http://ant.apache.org/ivy/ivyde/history/trunk/dev/updatesite.html(as
> >>>>>>>>> included-by-reference in the former) in preparing the above. That
> >>>>>> said, it
> >>>>>>>>> appears that I missed step 12 (and, accordingly, have a 1.4.0-rc1
> >>>>>> branch,
> >>>>>>>>> from the present tip of which the binaries were built, but no
> >>>>>> associated
> >>>>>>>>> tag).
> >>>>>>>>>
> >>>>>>>>> I'll be sure to get KEYS up-to-date. Thank you for the pointers.
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>> On Tue, Jan 21, 2014 at 6:26 AM, Stefan Bodewig <
> >>>> bodewig@apache.org
> >>>>>>> wrote:
> >>>>>>>>>
> >>>>>>>>>> Hi Charles,
> >>>>>>>>>>
> >>>>>>>>>> we don't really release binaries, they are just a convenience.
> >>>> All
> >>>>>> that
> >>>>>>>>>> matters as a release is the sources.
> >>>>>>>>>>
> >>>>>>>>>> I'm not sure there is anything documenting the release process
> for
> >>>>> Ivy
> >>>>>>>>>> but in general you create an svn tag and build source and binary
> >>>>>>>>>> distributions from that.
> >>>>>>>>>>
> >>>>>>>>>> What you have built now is a binary for testing and you don't
> >>>> really
> >>>>>>>>>> need to vote on that at all. Just encourage people to try it
> out
> >>>>> :-)
> >>>>>>>>>>
> >>>>>>>>>> If you want to perform some sort of test-release, have a look at
> >>>>>>>>>> <
> http://svn.apache.org/repos/asf/ant/antlibs/ReleaseInstructions>
> >>>>> and
> >>>>>>>>>> similar instructions to get an idea of what is expected.
> >>>>>>>>>>
> >>>>>>>>>>> PS -- As this build was performed on hardware owned by Indeed,
> >>>>> Inc.,
> >>>>>> the
> >>>>>>>>>>> binaries are signed with the duffy@indeed.com GPG key. For any
> >>>>> final
> >>>>>>>>>>> release, I would be using hardware under personal control and a
> >>>> key
> >>>>>>>>>>> associated with cduffy@apache.org.
> >>>>>>>>>>
> >>>>>>>>>> Please make sure whatever key you use is inside
> >>>>>>>>>> https://dist.apache.org/repos/dist/release/ant/KEYS - if you
> need
> >>>>> any
> >>>>>>>>>> help committing it there, please yell.
> >>>>>>>>>>
> >>>>>>>>>> Cheers
> >>>>>>>>>>
> >>>>>>>>>> Stefan
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>> ---------------------------------------------------------------------
> >>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
> >>>>>>>>>> For additional commands, e-mail: dev-help@ant.apache.org
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>>
> ---------------------------------------------------------------------
> >>>>>>> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
> >>>>>>> For additional commands, e-mail: dev-help@ant.apache.org
> >>>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> ---------------------------------------------------------------------
> >>>>>> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
> >>>>>> For additional commands, e-mail: dev-help@ant.apache.org
> >>>>>>
> >>>>>>
> >>>>>
> >>>>
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
> >> For additional commands, e-mail: dev-help@ant.apache.org
> >>
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
> For additional commands, e-mail: dev-help@ant.apache.org
>
>
Re: [VOTE] Ivy 2.4.0-rc1 Release
Posted by Charles Duffy <ch...@dyfis.net>.
If you could finish up, that would be very much appreciated. Whereas my
former employer allowed for some amount of Ivy work on business hours, such
is no longer the case, and my personal time has more demands than I'm
presently able to satisfy.
Thank you kindly, and please accept my apologies.
On Tue, Mar 4, 2014 at 8:46 PM, Antoine Levy Lambert <an...@gmx.de> wrote:
> Charles,
>
> are you going to be able to finish the release ?
>
> Do you need some help ?
>
> Best regards,
>
> Antoine
> On Feb 25, 2014, at 8:18 AM, Antoine Levy Lambert <an...@gmx.de> wrote:
>
> > Hi,
> >
> > I still do not see the public GPG key of Charles under
> https://dist.apache.org/repos/dist/release/ant/KEYS
> >
> > I did the following checkout to create a small sandbox with this KEYS
> file in it :
> >
> >
> >
> > svn checkout --depth=files --depth=files
> https://dist.apache.org/repos/dist/release/ant/ dist-release-ant
> >
> > Charles, let us know if you can check in your public key there.
> >
> >
> >
> > Antoine
> >
> >
> >
> > On Feb 15, 2014, at 9:23 AM, Nicolas Lalevée <ni...@hibnet.org>
> wrote:
> >
> >> Note that the release if not accepted yet, it cannot be published.
> >>
> >> Nicolas
> >>
> >> Le 14 févr. 2014 à 14:55, Charles Duffy <ch...@dyfis.net> a écrit :
> >>
> >>> Apologies -- new job; I dropped the ball somewhat. I'll try to get
> things
> >>> back on track this weekend.
> >>>
> >>>
> >>> On Fri, Feb 14, 2014 at 1:58 AM, Jean-Louis Boudart <
> >>> jeanlouis.boudart@gmail.com> wrote:
> >>>
> >>>> Is the release over ?
> >>>>
> >>>> I dont find it on maven central
> >>>> Le 28 janv. 2014 01:46, "Charles Duffy" <ch...@dyfis.net> a écrit :
> >>>>
> >>>>> The keys are actually different -- the one used by the
> currently-posted
> >>>>> .asc files is associated with Indeed, Inc. I'll be resigning the
> binaries
> >>>>> after verifying that their Indeed signatures are intact (and moving
> them
> >>>> to
> >>>>> dist.apache.org at that time).
> >>>>>
> >>>>> Expect a note in this thread when that happens.
> >>>>>
> >>>>>
> >>>>> On Mon, Jan 27, 2014 at 6:42 PM, Nicolas Lalevée <
> >>>>> nicolas.lalevee@hibnet.org
> >>>>>> wrote:
> >>>>>
> >>>>>>
> >>>>>> Le 22 janv. 2014 à 00:52, Nicolas Lalevée <
> nicolas.lalevee@hibnet.org>
> >>>> a
> >>>>>> écrit :
> >>>>>>
> >>>>>>> I have found some issues. The source distribution seems to miss
> some
> >>>>>> test files. I guess this has been the case for quite some time. And
> it
> >>>> is
> >>>>>> "just" about the tests. And it is an RC. So OK for me. And I will
> fix
> >>>>> that
> >>>>>> soon in trunk.
> >>>>>>>
> >>>>>>> To avoid confusion and make things simpler, I suggest we modify the
> >>>>>> release process to that everything goes through the svn of
> >>>>> dist.apache.org,
> >>>>>> and not use anymore people.apache.org. In the end, everything is
> >>>>>> published there.
> >>>>>>> And I'll modify in the doc of the release process the template of
> the
> >>>>>> email of the vote to include a line that is referencing the svn
> tag. So
> >>>>>> it's more difficult to miss it, and it is helpful to do review.
> >>>>>>>
> >>>>>>> I have tested the staging update site: works like a charm.
> >>>>>>>
> >>>>>>> So LGTM.
> >>>>>>>
> >>>>>>> I will cast my vote as soon as I can verify the signature of the
> >>>>>> artifacts.
> >>>>>>
> >>>>>> You pushed some keys to the KEYS files, but it doesn't seems to be
> the
> >>>>>> same as the one you used to sign the proposed artifacts.
> >>>>>>
> >>>>>> My gpg is asking for the key ID 93FB868A. Did I do something wrong
> or
> >>>> the
> >>>>>> keys are actually different ?
> >>>>>>
> >>>>>> Nicolas
> >>>>>>
> >>>>>>
> >>>>>>>
> >>>>>>> Nicolas
> >>>>>>>
> >>>>>>> Le 21 janv. 2014 à 17:19, Charles Duffy <ch...@dyfis.net> a
> écrit
> >>>> :
> >>>>>>>
> >>>>>>>> FYI --
> >>>>>>>>
> >>>>>>>> A tag at
> >>>>> https://svn.apache.org/repos/asf/ant/ivy/core/tags/2.4.0-rc1now
> >>>>>>>> exists. This differs from the branch head from which the binaries
> >>>> for
> >>>>>> test
> >>>>>>>> were built only inasmuch as its svn:externals specify a specific
> >>>>>> revision
> >>>>>>>> of the documentation build tools rather than leaving their
> revision
> >>>>>>>> floating.
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> On Tue, Jan 21, 2014 at 6:54 AM, Charles Duffy <charles@dyfis.net
> >
> >>>>>> wrote:
> >>>>>>>>
> >>>>>>>>> Howdy --
> >>>>>>>>>
> >>>>>>>>> I've attempted to follow the documentation at
> >>>>>>>>> http://ant.apache.org/ivy/history/trunk/dev/makerelease.html and
> >>>>>>>>>
> >>>> http://ant.apache.org/ivy/ivyde/history/trunk/dev/updatesite.html(as
> >>>>>>>>> included-by-reference in the former) in preparing the above. That
> >>>>>> said, it
> >>>>>>>>> appears that I missed step 12 (and, accordingly, have a 1.4.0-rc1
> >>>>>> branch,
> >>>>>>>>> from the present tip of which the binaries were built, but no
> >>>>>> associated
> >>>>>>>>> tag).
> >>>>>>>>>
> >>>>>>>>> I'll be sure to get KEYS up-to-date. Thank you for the pointers.
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>> On Tue, Jan 21, 2014 at 6:26 AM, Stefan Bodewig <
> >>>> bodewig@apache.org
> >>>>>>> wrote:
> >>>>>>>>>
> >>>>>>>>>> Hi Charles,
> >>>>>>>>>>
> >>>>>>>>>> we don't really release binaries, they are just a convenience.
> >>>> All
> >>>>>> that
> >>>>>>>>>> matters as a release is the sources.
> >>>>>>>>>>
> >>>>>>>>>> I'm not sure there is anything documenting the release process
> for
> >>>>> Ivy
> >>>>>>>>>> but in general you create an svn tag and build source and binary
> >>>>>>>>>> distributions from that.
> >>>>>>>>>>
> >>>>>>>>>> What you have built now is a binary for testing and you don't
> >>>> really
> >>>>>>>>>> need to vote on that at all. Just encourage people to try it
> out
> >>>>> :-)
> >>>>>>>>>>
> >>>>>>>>>> If you want to perform some sort of test-release, have a look at
> >>>>>>>>>> <
> http://svn.apache.org/repos/asf/ant/antlibs/ReleaseInstructions>
> >>>>> and
> >>>>>>>>>> similar instructions to get an idea of what is expected.
> >>>>>>>>>>
> >>>>>>>>>>> PS -- As this build was performed on hardware owned by Indeed,
> >>>>> Inc.,
> >>>>>> the
> >>>>>>>>>>> binaries are signed with the duffy@indeed.com GPG key. For any
> >>>>> final
> >>>>>>>>>>> release, I would be using hardware under personal control and a
> >>>> key
> >>>>>>>>>>> associated with cduffy@apache.org.
> >>>>>>>>>>
> >>>>>>>>>> Please make sure whatever key you use is inside
> >>>>>>>>>> https://dist.apache.org/repos/dist/release/ant/KEYS - if you
> need
> >>>>> any
> >>>>>>>>>> help committing it there, please yell.
> >>>>>>>>>>
> >>>>>>>>>> Cheers
> >>>>>>>>>>
> >>>>>>>>>> Stefan
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>> ---------------------------------------------------------------------
> >>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
> >>>>>>>>>> For additional commands, e-mail: dev-help@ant.apache.org
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>>
> ---------------------------------------------------------------------
> >>>>>>> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
> >>>>>>> For additional commands, e-mail: dev-help@ant.apache.org
> >>>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> ---------------------------------------------------------------------
> >>>>>> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
> >>>>>> For additional commands, e-mail: dev-help@ant.apache.org
> >>>>>>
> >>>>>>
> >>>>>
> >>>>
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
> >> For additional commands, e-mail: dev-help@ant.apache.org
> >>
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
> For additional commands, e-mail: dev-help@ant.apache.org
>
>
Re: [VOTE] Ivy 2.4.0-rc1 Release
Posted by Antoine Levy Lambert <an...@gmx.de>.
Charles,
are you going to be able to finish the release ?
Do you need some help ?
Best regards,
Antoine
On Feb 25, 2014, at 8:18 AM, Antoine Levy Lambert <an...@gmx.de> wrote:
> Hi,
>
> I still do not see the public GPG key of Charles under https://dist.apache.org/repos/dist/release/ant/KEYS
>
> I did the following checkout to create a small sandbox with this KEYS file in it :
>
>
>
> svn checkout --depth=files --depth=files https://dist.apache.org/repos/dist/release/ant/ dist-release-ant
>
> Charles, let us know if you can check in your public key there.
>
>
>
> Antoine
>
>
>
> On Feb 15, 2014, at 9:23 AM, Nicolas Lalevée <ni...@hibnet.org> wrote:
>
>> Note that the release if not accepted yet, it cannot be published.
>>
>> Nicolas
>>
>> Le 14 févr. 2014 à 14:55, Charles Duffy <ch...@dyfis.net> a écrit :
>>
>>> Apologies -- new job; I dropped the ball somewhat. I'll try to get things
>>> back on track this weekend.
>>>
>>>
>>> On Fri, Feb 14, 2014 at 1:58 AM, Jean-Louis Boudart <
>>> jeanlouis.boudart@gmail.com> wrote:
>>>
>>>> Is the release over ?
>>>>
>>>> I dont find it on maven central
>>>> Le 28 janv. 2014 01:46, "Charles Duffy" <ch...@dyfis.net> a écrit :
>>>>
>>>>> The keys are actually different -- the one used by the currently-posted
>>>>> .asc files is associated with Indeed, Inc. I'll be resigning the binaries
>>>>> after verifying that their Indeed signatures are intact (and moving them
>>>> to
>>>>> dist.apache.org at that time).
>>>>>
>>>>> Expect a note in this thread when that happens.
>>>>>
>>>>>
>>>>> On Mon, Jan 27, 2014 at 6:42 PM, Nicolas Lalevée <
>>>>> nicolas.lalevee@hibnet.org
>>>>>> wrote:
>>>>>
>>>>>>
>>>>>> Le 22 janv. 2014 à 00:52, Nicolas Lalevée <ni...@hibnet.org>
>>>> a
>>>>>> écrit :
>>>>>>
>>>>>>> I have found some issues. The source distribution seems to miss some
>>>>>> test files. I guess this has been the case for quite some time. And it
>>>> is
>>>>>> "just" about the tests. And it is an RC. So OK for me. And I will fix
>>>>> that
>>>>>> soon in trunk.
>>>>>>>
>>>>>>> To avoid confusion and make things simpler, I suggest we modify the
>>>>>> release process to that everything goes through the svn of
>>>>> dist.apache.org,
>>>>>> and not use anymore people.apache.org. In the end, everything is
>>>>>> published there.
>>>>>>> And I'll modify in the doc of the release process the template of the
>>>>>> email of the vote to include a line that is referencing the svn tag. So
>>>>>> it's more difficult to miss it, and it is helpful to do review.
>>>>>>>
>>>>>>> I have tested the staging update site: works like a charm.
>>>>>>>
>>>>>>> So LGTM.
>>>>>>>
>>>>>>> I will cast my vote as soon as I can verify the signature of the
>>>>>> artifacts.
>>>>>>
>>>>>> You pushed some keys to the KEYS files, but it doesn't seems to be the
>>>>>> same as the one you used to sign the proposed artifacts.
>>>>>>
>>>>>> My gpg is asking for the key ID 93FB868A. Did I do something wrong or
>>>> the
>>>>>> keys are actually different ?
>>>>>>
>>>>>> Nicolas
>>>>>>
>>>>>>
>>>>>>>
>>>>>>> Nicolas
>>>>>>>
>>>>>>> Le 21 janv. 2014 à 17:19, Charles Duffy <ch...@dyfis.net> a écrit
>>>> :
>>>>>>>
>>>>>>>> FYI --
>>>>>>>>
>>>>>>>> A tag at
>>>>> https://svn.apache.org/repos/asf/ant/ivy/core/tags/2.4.0-rc1now
>>>>>>>> exists. This differs from the branch head from which the binaries
>>>> for
>>>>>> test
>>>>>>>> were built only inasmuch as its svn:externals specify a specific
>>>>>> revision
>>>>>>>> of the documentation build tools rather than leaving their revision
>>>>>>>> floating.
>>>>>>>>
>>>>>>>>
>>>>>>>> On Tue, Jan 21, 2014 at 6:54 AM, Charles Duffy <ch...@dyfis.net>
>>>>>> wrote:
>>>>>>>>
>>>>>>>>> Howdy --
>>>>>>>>>
>>>>>>>>> I've attempted to follow the documentation at
>>>>>>>>> http://ant.apache.org/ivy/history/trunk/dev/makerelease.html and
>>>>>>>>>
>>>> http://ant.apache.org/ivy/ivyde/history/trunk/dev/updatesite.html(as
>>>>>>>>> included-by-reference in the former) in preparing the above. That
>>>>>> said, it
>>>>>>>>> appears that I missed step 12 (and, accordingly, have a 1.4.0-rc1
>>>>>> branch,
>>>>>>>>> from the present tip of which the binaries were built, but no
>>>>>> associated
>>>>>>>>> tag).
>>>>>>>>>
>>>>>>>>> I'll be sure to get KEYS up-to-date. Thank you for the pointers.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Tue, Jan 21, 2014 at 6:26 AM, Stefan Bodewig <
>>>> bodewig@apache.org
>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>> Hi Charles,
>>>>>>>>>>
>>>>>>>>>> we don't really release binaries, they are just a convenience.
>>>> All
>>>>>> that
>>>>>>>>>> matters as a release is the sources.
>>>>>>>>>>
>>>>>>>>>> I'm not sure there is anything documenting the release process for
>>>>> Ivy
>>>>>>>>>> but in general you create an svn tag and build source and binary
>>>>>>>>>> distributions from that.
>>>>>>>>>>
>>>>>>>>>> What you have built now is a binary for testing and you don't
>>>> really
>>>>>>>>>> need to vote on that at all. Just encourage people to try it out
>>>>> :-)
>>>>>>>>>>
>>>>>>>>>> If you want to perform some sort of test-release, have a look at
>>>>>>>>>> <http://svn.apache.org/repos/asf/ant/antlibs/ReleaseInstructions>
>>>>> and
>>>>>>>>>> similar instructions to get an idea of what is expected.
>>>>>>>>>>
>>>>>>>>>>> PS -- As this build was performed on hardware owned by Indeed,
>>>>> Inc.,
>>>>>> the
>>>>>>>>>>> binaries are signed with the duffy@indeed.com GPG key. For any
>>>>> final
>>>>>>>>>>> release, I would be using hardware under personal control and a
>>>> key
>>>>>>>>>>> associated with cduffy@apache.org.
>>>>>>>>>>
>>>>>>>>>> Please make sure whatever key you use is inside
>>>>>>>>>> https://dist.apache.org/repos/dist/release/ant/KEYS - if you need
>>>>> any
>>>>>>>>>> help committing it there, please yell.
>>>>>>>>>>
>>>>>>>>>> Cheers
>>>>>>>>>>
>>>>>>>>>> Stefan
>>>>>>>>>>
>>>>>>>>>>
>>>>> ---------------------------------------------------------------------
>>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
>>>>>>>>>> For additional commands, e-mail: dev-help@ant.apache.org
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> ---------------------------------------------------------------------
>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
>>>>>>> For additional commands, e-mail: dev-help@ant.apache.org
>>>>>>>
>>>>>>
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
>>>>>> For additional commands, e-mail: dev-help@ant.apache.org
>>>>>>
>>>>>>
>>>>>
>>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
>> For additional commands, e-mail: dev-help@ant.apache.org
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org
Re: [VOTE] Ivy 2.4.0-rc1 Release
Posted by Antoine Levy Lambert <an...@gmx.de>.
Hi,
I still do not see the public GPG key of Charles under https://dist.apache.org/repos/dist/release/ant/KEYS
I did the following checkout to create a small sandbox with this KEYS file in it :
svn checkout --depth=files --depth=files https://dist.apache.org/repos/dist/release/ant/ dist-release-ant
Charles, let us know if you can check in your public key there.
Antoine
On Feb 15, 2014, at 9:23 AM, Nicolas Lalevée <ni...@hibnet.org> wrote:
> Note that the release if not accepted yet, it cannot be published.
>
> Nicolas
>
> Le 14 févr. 2014 à 14:55, Charles Duffy <ch...@dyfis.net> a écrit :
>
>> Apologies -- new job; I dropped the ball somewhat. I'll try to get things
>> back on track this weekend.
>>
>>
>> On Fri, Feb 14, 2014 at 1:58 AM, Jean-Louis Boudart <
>> jeanlouis.boudart@gmail.com> wrote:
>>
>>> Is the release over ?
>>>
>>> I dont find it on maven central
>>> Le 28 janv. 2014 01:46, "Charles Duffy" <ch...@dyfis.net> a écrit :
>>>
>>>> The keys are actually different -- the one used by the currently-posted
>>>> .asc files is associated with Indeed, Inc. I'll be resigning the binaries
>>>> after verifying that their Indeed signatures are intact (and moving them
>>> to
>>>> dist.apache.org at that time).
>>>>
>>>> Expect a note in this thread when that happens.
>>>>
>>>>
>>>> On Mon, Jan 27, 2014 at 6:42 PM, Nicolas Lalevée <
>>>> nicolas.lalevee@hibnet.org
>>>>> wrote:
>>>>
>>>>>
>>>>> Le 22 janv. 2014 à 00:52, Nicolas Lalevée <ni...@hibnet.org>
>>> a
>>>>> écrit :
>>>>>
>>>>>> I have found some issues. The source distribution seems to miss some
>>>>> test files. I guess this has been the case for quite some time. And it
>>> is
>>>>> "just" about the tests. And it is an RC. So OK for me. And I will fix
>>>> that
>>>>> soon in trunk.
>>>>>>
>>>>>> To avoid confusion and make things simpler, I suggest we modify the
>>>>> release process to that everything goes through the svn of
>>>> dist.apache.org,
>>>>> and not use anymore people.apache.org. In the end, everything is
>>>>> published there.
>>>>>> And I'll modify in the doc of the release process the template of the
>>>>> email of the vote to include a line that is referencing the svn tag. So
>>>>> it's more difficult to miss it, and it is helpful to do review.
>>>>>>
>>>>>> I have tested the staging update site: works like a charm.
>>>>>>
>>>>>> So LGTM.
>>>>>>
>>>>>> I will cast my vote as soon as I can verify the signature of the
>>>>> artifacts.
>>>>>
>>>>> You pushed some keys to the KEYS files, but it doesn't seems to be the
>>>>> same as the one you used to sign the proposed artifacts.
>>>>>
>>>>> My gpg is asking for the key ID 93FB868A. Did I do something wrong or
>>> the
>>>>> keys are actually different ?
>>>>>
>>>>> Nicolas
>>>>>
>>>>>
>>>>>>
>>>>>> Nicolas
>>>>>>
>>>>>> Le 21 janv. 2014 à 17:19, Charles Duffy <ch...@dyfis.net> a écrit
>>> :
>>>>>>
>>>>>>> FYI --
>>>>>>>
>>>>>>> A tag at
>>>> https://svn.apache.org/repos/asf/ant/ivy/core/tags/2.4.0-rc1now
>>>>>>> exists. This differs from the branch head from which the binaries
>>> for
>>>>> test
>>>>>>> were built only inasmuch as its svn:externals specify a specific
>>>>> revision
>>>>>>> of the documentation build tools rather than leaving their revision
>>>>>>> floating.
>>>>>>>
>>>>>>>
>>>>>>> On Tue, Jan 21, 2014 at 6:54 AM, Charles Duffy <ch...@dyfis.net>
>>>>> wrote:
>>>>>>>
>>>>>>>> Howdy --
>>>>>>>>
>>>>>>>> I've attempted to follow the documentation at
>>>>>>>> http://ant.apache.org/ivy/history/trunk/dev/makerelease.html and
>>>>>>>>
>>> http://ant.apache.org/ivy/ivyde/history/trunk/dev/updatesite.html(as
>>>>>>>> included-by-reference in the former) in preparing the above. That
>>>>> said, it
>>>>>>>> appears that I missed step 12 (and, accordingly, have a 1.4.0-rc1
>>>>> branch,
>>>>>>>> from the present tip of which the binaries were built, but no
>>>>> associated
>>>>>>>> tag).
>>>>>>>>
>>>>>>>> I'll be sure to get KEYS up-to-date. Thank you for the pointers.
>>>>>>>>
>>>>>>>>
>>>>>>>> On Tue, Jan 21, 2014 at 6:26 AM, Stefan Bodewig <
>>> bodewig@apache.org
>>>>>> wrote:
>>>>>>>>
>>>>>>>>> Hi Charles,
>>>>>>>>>
>>>>>>>>> we don't really release binaries, they are just a convenience.
>>> All
>>>>> that
>>>>>>>>> matters as a release is the sources.
>>>>>>>>>
>>>>>>>>> I'm not sure there is anything documenting the release process for
>>>> Ivy
>>>>>>>>> but in general you create an svn tag and build source and binary
>>>>>>>>> distributions from that.
>>>>>>>>>
>>>>>>>>> What you have built now is a binary for testing and you don't
>>> really
>>>>>>>>> need to vote on that at all. Just encourage people to try it out
>>>> :-)
>>>>>>>>>
>>>>>>>>> If you want to perform some sort of test-release, have a look at
>>>>>>>>> <http://svn.apache.org/repos/asf/ant/antlibs/ReleaseInstructions>
>>>> and
>>>>>>>>> similar instructions to get an idea of what is expected.
>>>>>>>>>
>>>>>>>>>> PS -- As this build was performed on hardware owned by Indeed,
>>>> Inc.,
>>>>> the
>>>>>>>>>> binaries are signed with the duffy@indeed.com GPG key. For any
>>>> final
>>>>>>>>>> release, I would be using hardware under personal control and a
>>> key
>>>>>>>>>> associated with cduffy@apache.org.
>>>>>>>>>
>>>>>>>>> Please make sure whatever key you use is inside
>>>>>>>>> https://dist.apache.org/repos/dist/release/ant/KEYS - if you need
>>>> any
>>>>>>>>> help committing it there, please yell.
>>>>>>>>>
>>>>>>>>> Cheers
>>>>>>>>>
>>>>>>>>> Stefan
>>>>>>>>>
>>>>>>>>>
>>>> ---------------------------------------------------------------------
>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
>>>>>>>>> For additional commands, e-mail: dev-help@ant.apache.org
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
>>>>>> For additional commands, e-mail: dev-help@ant.apache.org
>>>>>>
>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
>>>>> For additional commands, e-mail: dev-help@ant.apache.org
>>>>>
>>>>>
>>>>
>>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
> For additional commands, e-mail: dev-help@ant.apache.org
>
Re: [VOTE] Ivy 2.4.0-rc1 Release
Posted by Nicolas Lalevée <ni...@hibnet.org>.
Note that the release if not accepted yet, it cannot be published.
Nicolas
Le 14 févr. 2014 à 14:55, Charles Duffy <ch...@dyfis.net> a écrit :
> Apologies -- new job; I dropped the ball somewhat. I'll try to get things
> back on track this weekend.
>
>
> On Fri, Feb 14, 2014 at 1:58 AM, Jean-Louis Boudart <
> jeanlouis.boudart@gmail.com> wrote:
>
>> Is the release over ?
>>
>> I dont find it on maven central
>> Le 28 janv. 2014 01:46, "Charles Duffy" <ch...@dyfis.net> a écrit :
>>
>>> The keys are actually different -- the one used by the currently-posted
>>> .asc files is associated with Indeed, Inc. I'll be resigning the binaries
>>> after verifying that their Indeed signatures are intact (and moving them
>> to
>>> dist.apache.org at that time).
>>>
>>> Expect a note in this thread when that happens.
>>>
>>>
>>> On Mon, Jan 27, 2014 at 6:42 PM, Nicolas Lalevée <
>>> nicolas.lalevee@hibnet.org
>>>> wrote:
>>>
>>>>
>>>> Le 22 janv. 2014 à 00:52, Nicolas Lalevée <ni...@hibnet.org>
>> a
>>>> écrit :
>>>>
>>>>> I have found some issues. The source distribution seems to miss some
>>>> test files. I guess this has been the case for quite some time. And it
>> is
>>>> "just" about the tests. And it is an RC. So OK for me. And I will fix
>>> that
>>>> soon in trunk.
>>>>>
>>>>> To avoid confusion and make things simpler, I suggest we modify the
>>>> release process to that everything goes through the svn of
>>> dist.apache.org,
>>>> and not use anymore people.apache.org. In the end, everything is
>>>> published there.
>>>>> And I'll modify in the doc of the release process the template of the
>>>> email of the vote to include a line that is referencing the svn tag. So
>>>> it's more difficult to miss it, and it is helpful to do review.
>>>>>
>>>>> I have tested the staging update site: works like a charm.
>>>>>
>>>>> So LGTM.
>>>>>
>>>>> I will cast my vote as soon as I can verify the signature of the
>>>> artifacts.
>>>>
>>>> You pushed some keys to the KEYS files, but it doesn't seems to be the
>>>> same as the one you used to sign the proposed artifacts.
>>>>
>>>> My gpg is asking for the key ID 93FB868A. Did I do something wrong or
>> the
>>>> keys are actually different ?
>>>>
>>>> Nicolas
>>>>
>>>>
>>>>>
>>>>> Nicolas
>>>>>
>>>>> Le 21 janv. 2014 à 17:19, Charles Duffy <ch...@dyfis.net> a écrit
>> :
>>>>>
>>>>>> FYI --
>>>>>>
>>>>>> A tag at
>>> https://svn.apache.org/repos/asf/ant/ivy/core/tags/2.4.0-rc1now
>>>>>> exists. This differs from the branch head from which the binaries
>> for
>>>> test
>>>>>> were built only inasmuch as its svn:externals specify a specific
>>>> revision
>>>>>> of the documentation build tools rather than leaving their revision
>>>>>> floating.
>>>>>>
>>>>>>
>>>>>> On Tue, Jan 21, 2014 at 6:54 AM, Charles Duffy <ch...@dyfis.net>
>>>> wrote:
>>>>>>
>>>>>>> Howdy --
>>>>>>>
>>>>>>> I've attempted to follow the documentation at
>>>>>>> http://ant.apache.org/ivy/history/trunk/dev/makerelease.html and
>>>>>>>
>> http://ant.apache.org/ivy/ivyde/history/trunk/dev/updatesite.html(as
>>>>>>> included-by-reference in the former) in preparing the above. That
>>>> said, it
>>>>>>> appears that I missed step 12 (and, accordingly, have a 1.4.0-rc1
>>>> branch,
>>>>>>> from the present tip of which the binaries were built, but no
>>>> associated
>>>>>>> tag).
>>>>>>>
>>>>>>> I'll be sure to get KEYS up-to-date. Thank you for the pointers.
>>>>>>>
>>>>>>>
>>>>>>> On Tue, Jan 21, 2014 at 6:26 AM, Stefan Bodewig <
>> bodewig@apache.org
>>>>> wrote:
>>>>>>>
>>>>>>>> Hi Charles,
>>>>>>>>
>>>>>>>> we don't really release binaries, they are just a convenience.
>> All
>>>> that
>>>>>>>> matters as a release is the sources.
>>>>>>>>
>>>>>>>> I'm not sure there is anything documenting the release process for
>>> Ivy
>>>>>>>> but in general you create an svn tag and build source and binary
>>>>>>>> distributions from that.
>>>>>>>>
>>>>>>>> What you have built now is a binary for testing and you don't
>> really
>>>>>>>> need to vote on that at all. Just encourage people to try it out
>>> :-)
>>>>>>>>
>>>>>>>> If you want to perform some sort of test-release, have a look at
>>>>>>>> <http://svn.apache.org/repos/asf/ant/antlibs/ReleaseInstructions>
>>> and
>>>>>>>> similar instructions to get an idea of what is expected.
>>>>>>>>
>>>>>>>>> PS -- As this build was performed on hardware owned by Indeed,
>>> Inc.,
>>>> the
>>>>>>>>> binaries are signed with the duffy@indeed.com GPG key. For any
>>> final
>>>>>>>>> release, I would be using hardware under personal control and a
>> key
>>>>>>>>> associated with cduffy@apache.org.
>>>>>>>>
>>>>>>>> Please make sure whatever key you use is inside
>>>>>>>> https://dist.apache.org/repos/dist/release/ant/KEYS - if you need
>>> any
>>>>>>>> help committing it there, please yell.
>>>>>>>>
>>>>>>>> Cheers
>>>>>>>>
>>>>>>>> Stefan
>>>>>>>>
>>>>>>>>
>>> ---------------------------------------------------------------------
>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
>>>>>>>> For additional commands, e-mail: dev-help@ant.apache.org
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
>>>>> For additional commands, e-mail: dev-help@ant.apache.org
>>>>>
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
>>>> For additional commands, e-mail: dev-help@ant.apache.org
>>>>
>>>>
>>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org
Re: [VOTE] Ivy 2.4.0-rc1 Release
Posted by Charles Duffy <ch...@dyfis.net>.
Apologies -- new job; I dropped the ball somewhat. I'll try to get things
back on track this weekend.
On Fri, Feb 14, 2014 at 1:58 AM, Jean-Louis Boudart <
jeanlouis.boudart@gmail.com> wrote:
> Is the release over ?
>
> I dont find it on maven central
> Le 28 janv. 2014 01:46, "Charles Duffy" <ch...@dyfis.net> a écrit :
>
> > The keys are actually different -- the one used by the currently-posted
> > .asc files is associated with Indeed, Inc. I'll be resigning the binaries
> > after verifying that their Indeed signatures are intact (and moving them
> to
> > dist.apache.org at that time).
> >
> > Expect a note in this thread when that happens.
> >
> >
> > On Mon, Jan 27, 2014 at 6:42 PM, Nicolas Lalevée <
> > nicolas.lalevee@hibnet.org
> > > wrote:
> >
> > >
> > > Le 22 janv. 2014 à 00:52, Nicolas Lalevée <ni...@hibnet.org>
> a
> > > écrit :
> > >
> > > > I have found some issues. The source distribution seems to miss some
> > > test files. I guess this has been the case for quite some time. And it
> is
> > > "just" about the tests. And it is an RC. So OK for me. And I will fix
> > that
> > > soon in trunk.
> > > >
> > > > To avoid confusion and make things simpler, I suggest we modify the
> > > release process to that everything goes through the svn of
> > dist.apache.org,
> > > and not use anymore people.apache.org. In the end, everything is
> > > published there.
> > > > And I'll modify in the doc of the release process the template of the
> > > email of the vote to include a line that is referencing the svn tag. So
> > > it's more difficult to miss it, and it is helpful to do review.
> > > >
> > > > I have tested the staging update site: works like a charm.
> > > >
> > > > So LGTM.
> > > >
> > > > I will cast my vote as soon as I can verify the signature of the
> > > artifacts.
> > >
> > > You pushed some keys to the KEYS files, but it doesn't seems to be the
> > > same as the one you used to sign the proposed artifacts.
> > >
> > > My gpg is asking for the key ID 93FB868A. Did I do something wrong or
> the
> > > keys are actually different ?
> > >
> > > Nicolas
> > >
> > >
> > > >
> > > > Nicolas
> > > >
> > > > Le 21 janv. 2014 à 17:19, Charles Duffy <ch...@dyfis.net> a écrit
> :
> > > >
> > > >> FYI --
> > > >>
> > > >> A tag at
> > https://svn.apache.org/repos/asf/ant/ivy/core/tags/2.4.0-rc1now
> > > >> exists. This differs from the branch head from which the binaries
> for
> > > test
> > > >> were built only inasmuch as its svn:externals specify a specific
> > > revision
> > > >> of the documentation build tools rather than leaving their revision
> > > >> floating.
> > > >>
> > > >>
> > > >> On Tue, Jan 21, 2014 at 6:54 AM, Charles Duffy <ch...@dyfis.net>
> > > wrote:
> > > >>
> > > >>> Howdy --
> > > >>>
> > > >>> I've attempted to follow the documentation at
> > > >>> http://ant.apache.org/ivy/history/trunk/dev/makerelease.html and
> > > >>>
> http://ant.apache.org/ivy/ivyde/history/trunk/dev/updatesite.html(as
> > > >>> included-by-reference in the former) in preparing the above. That
> > > said, it
> > > >>> appears that I missed step 12 (and, accordingly, have a 1.4.0-rc1
> > > branch,
> > > >>> from the present tip of which the binaries were built, but no
> > > associated
> > > >>> tag).
> > > >>>
> > > >>> I'll be sure to get KEYS up-to-date. Thank you for the pointers.
> > > >>>
> > > >>>
> > > >>> On Tue, Jan 21, 2014 at 6:26 AM, Stefan Bodewig <
> bodewig@apache.org
> > > >wrote:
> > > >>>
> > > >>>> Hi Charles,
> > > >>>>
> > > >>>> we don't really release binaries, they are just a convenience.
> All
> > > that
> > > >>>> matters as a release is the sources.
> > > >>>>
> > > >>>> I'm not sure there is anything documenting the release process for
> > Ivy
> > > >>>> but in general you create an svn tag and build source and binary
> > > >>>> distributions from that.
> > > >>>>
> > > >>>> What you have built now is a binary for testing and you don't
> really
> > > >>>> need to vote on that at all. Just encourage people to try it out
> > :-)
> > > >>>>
> > > >>>> If you want to perform some sort of test-release, have a look at
> > > >>>> <http://svn.apache.org/repos/asf/ant/antlibs/ReleaseInstructions>
> > and
> > > >>>> similar instructions to get an idea of what is expected.
> > > >>>>
> > > >>>>> PS -- As this build was performed on hardware owned by Indeed,
> > Inc.,
> > > the
> > > >>>>> binaries are signed with the duffy@indeed.com GPG key. For any
> > final
> > > >>>>> release, I would be using hardware under personal control and a
> key
> > > >>>>> associated with cduffy@apache.org.
> > > >>>>
> > > >>>> Please make sure whatever key you use is inside
> > > >>>> https://dist.apache.org/repos/dist/release/ant/KEYS - if you need
> > any
> > > >>>> help committing it there, please yell.
> > > >>>>
> > > >>>> Cheers
> > > >>>>
> > > >>>> Stefan
> > > >>>>
> > > >>>>
> > ---------------------------------------------------------------------
> > > >>>> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
> > > >>>> For additional commands, e-mail: dev-help@ant.apache.org
> > > >>>>
> > > >>>>
> > > >>>
> > > >
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
> > > > For additional commands, e-mail: dev-help@ant.apache.org
> > > >
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
> > > For additional commands, e-mail: dev-help@ant.apache.org
> > >
> > >
> >
>
Re: [VOTE] Ivy 2.4.0-rc1 Release
Posted by Jean-Louis Boudart <je...@gmail.com>.
Is the release over ?
I dont find it on maven central
Le 28 janv. 2014 01:46, "Charles Duffy" <ch...@dyfis.net> a écrit :
> The keys are actually different -- the one used by the currently-posted
> .asc files is associated with Indeed, Inc. I'll be resigning the binaries
> after verifying that their Indeed signatures are intact (and moving them to
> dist.apache.org at that time).
>
> Expect a note in this thread when that happens.
>
>
> On Mon, Jan 27, 2014 at 6:42 PM, Nicolas Lalevée <
> nicolas.lalevee@hibnet.org
> > wrote:
>
> >
> > Le 22 janv. 2014 à 00:52, Nicolas Lalevée <ni...@hibnet.org> a
> > écrit :
> >
> > > I have found some issues. The source distribution seems to miss some
> > test files. I guess this has been the case for quite some time. And it is
> > "just" about the tests. And it is an RC. So OK for me. And I will fix
> that
> > soon in trunk.
> > >
> > > To avoid confusion and make things simpler, I suggest we modify the
> > release process to that everything goes through the svn of
> dist.apache.org,
> > and not use anymore people.apache.org. In the end, everything is
> > published there.
> > > And I'll modify in the doc of the release process the template of the
> > email of the vote to include a line that is referencing the svn tag. So
> > it's more difficult to miss it, and it is helpful to do review.
> > >
> > > I have tested the staging update site: works like a charm.
> > >
> > > So LGTM.
> > >
> > > I will cast my vote as soon as I can verify the signature of the
> > artifacts.
> >
> > You pushed some keys to the KEYS files, but it doesn't seems to be the
> > same as the one you used to sign the proposed artifacts.
> >
> > My gpg is asking for the key ID 93FB868A. Did I do something wrong or the
> > keys are actually different ?
> >
> > Nicolas
> >
> >
> > >
> > > Nicolas
> > >
> > > Le 21 janv. 2014 à 17:19, Charles Duffy <ch...@dyfis.net> a écrit :
> > >
> > >> FYI --
> > >>
> > >> A tag at
> https://svn.apache.org/repos/asf/ant/ivy/core/tags/2.4.0-rc1now
> > >> exists. This differs from the branch head from which the binaries for
> > test
> > >> were built only inasmuch as its svn:externals specify a specific
> > revision
> > >> of the documentation build tools rather than leaving their revision
> > >> floating.
> > >>
> > >>
> > >> On Tue, Jan 21, 2014 at 6:54 AM, Charles Duffy <ch...@dyfis.net>
> > wrote:
> > >>
> > >>> Howdy --
> > >>>
> > >>> I've attempted to follow the documentation at
> > >>> http://ant.apache.org/ivy/history/trunk/dev/makerelease.html and
> > >>> http://ant.apache.org/ivy/ivyde/history/trunk/dev/updatesite.html(as
> > >>> included-by-reference in the former) in preparing the above. That
> > said, it
> > >>> appears that I missed step 12 (and, accordingly, have a 1.4.0-rc1
> > branch,
> > >>> from the present tip of which the binaries were built, but no
> > associated
> > >>> tag).
> > >>>
> > >>> I'll be sure to get KEYS up-to-date. Thank you for the pointers.
> > >>>
> > >>>
> > >>> On Tue, Jan 21, 2014 at 6:26 AM, Stefan Bodewig <bodewig@apache.org
> > >wrote:
> > >>>
> > >>>> Hi Charles,
> > >>>>
> > >>>> we don't really release binaries, they are just a convenience. All
> > that
> > >>>> matters as a release is the sources.
> > >>>>
> > >>>> I'm not sure there is anything documenting the release process for
> Ivy
> > >>>> but in general you create an svn tag and build source and binary
> > >>>> distributions from that.
> > >>>>
> > >>>> What you have built now is a binary for testing and you don't really
> > >>>> need to vote on that at all. Just encourage people to try it out
> :-)
> > >>>>
> > >>>> If you want to perform some sort of test-release, have a look at
> > >>>> <http://svn.apache.org/repos/asf/ant/antlibs/ReleaseInstructions>
> and
> > >>>> similar instructions to get an idea of what is expected.
> > >>>>
> > >>>>> PS -- As this build was performed on hardware owned by Indeed,
> Inc.,
> > the
> > >>>>> binaries are signed with the duffy@indeed.com GPG key. For any
> final
> > >>>>> release, I would be using hardware under personal control and a key
> > >>>>> associated with cduffy@apache.org.
> > >>>>
> > >>>> Please make sure whatever key you use is inside
> > >>>> https://dist.apache.org/repos/dist/release/ant/KEYS - if you need
> any
> > >>>> help committing it there, please yell.
> > >>>>
> > >>>> Cheers
> > >>>>
> > >>>> Stefan
> > >>>>
> > >>>>
> ---------------------------------------------------------------------
> > >>>> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
> > >>>> For additional commands, e-mail: dev-help@ant.apache.org
> > >>>>
> > >>>>
> > >>>
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
> > > For additional commands, e-mail: dev-help@ant.apache.org
> > >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
> > For additional commands, e-mail: dev-help@ant.apache.org
> >
> >
>
Re: [VOTE] Ivy 2.4.0-rc1 Release
Posted by Charles Duffy <ch...@dyfis.net>.
The keys are actually different -- the one used by the currently-posted
.asc files is associated with Indeed, Inc. I'll be resigning the binaries
after verifying that their Indeed signatures are intact (and moving them to
dist.apache.org at that time).
Expect a note in this thread when that happens.
On Mon, Jan 27, 2014 at 6:42 PM, Nicolas Lalevée <nicolas.lalevee@hibnet.org
> wrote:
>
> Le 22 janv. 2014 à 00:52, Nicolas Lalevée <ni...@hibnet.org> a
> écrit :
>
> > I have found some issues. The source distribution seems to miss some
> test files. I guess this has been the case for quite some time. And it is
> "just" about the tests. And it is an RC. So OK for me. And I will fix that
> soon in trunk.
> >
> > To avoid confusion and make things simpler, I suggest we modify the
> release process to that everything goes through the svn of dist.apache.org,
> and not use anymore people.apache.org. In the end, everything is
> published there.
> > And I'll modify in the doc of the release process the template of the
> email of the vote to include a line that is referencing the svn tag. So
> it's more difficult to miss it, and it is helpful to do review.
> >
> > I have tested the staging update site: works like a charm.
> >
> > So LGTM.
> >
> > I will cast my vote as soon as I can verify the signature of the
> artifacts.
>
> You pushed some keys to the KEYS files, but it doesn't seems to be the
> same as the one you used to sign the proposed artifacts.
>
> My gpg is asking for the key ID 93FB868A. Did I do something wrong or the
> keys are actually different ?
>
> Nicolas
>
>
> >
> > Nicolas
> >
> > Le 21 janv. 2014 à 17:19, Charles Duffy <ch...@dyfis.net> a écrit :
> >
> >> FYI --
> >>
> >> A tag at https://svn.apache.org/repos/asf/ant/ivy/core/tags/2.4.0-rc1now
> >> exists. This differs from the branch head from which the binaries for
> test
> >> were built only inasmuch as its svn:externals specify a specific
> revision
> >> of the documentation build tools rather than leaving their revision
> >> floating.
> >>
> >>
> >> On Tue, Jan 21, 2014 at 6:54 AM, Charles Duffy <ch...@dyfis.net>
> wrote:
> >>
> >>> Howdy --
> >>>
> >>> I've attempted to follow the documentation at
> >>> http://ant.apache.org/ivy/history/trunk/dev/makerelease.html and
> >>> http://ant.apache.org/ivy/ivyde/history/trunk/dev/updatesite.html (as
> >>> included-by-reference in the former) in preparing the above. That
> said, it
> >>> appears that I missed step 12 (and, accordingly, have a 1.4.0-rc1
> branch,
> >>> from the present tip of which the binaries were built, but no
> associated
> >>> tag).
> >>>
> >>> I'll be sure to get KEYS up-to-date. Thank you for the pointers.
> >>>
> >>>
> >>> On Tue, Jan 21, 2014 at 6:26 AM, Stefan Bodewig <bodewig@apache.org
> >wrote:
> >>>
> >>>> Hi Charles,
> >>>>
> >>>> we don't really release binaries, they are just a convenience. All
> that
> >>>> matters as a release is the sources.
> >>>>
> >>>> I'm not sure there is anything documenting the release process for Ivy
> >>>> but in general you create an svn tag and build source and binary
> >>>> distributions from that.
> >>>>
> >>>> What you have built now is a binary for testing and you don't really
> >>>> need to vote on that at all. Just encourage people to try it out :-)
> >>>>
> >>>> If you want to perform some sort of test-release, have a look at
> >>>> <http://svn.apache.org/repos/asf/ant/antlibs/ReleaseInstructions> and
> >>>> similar instructions to get an idea of what is expected.
> >>>>
> >>>>> PS -- As this build was performed on hardware owned by Indeed, Inc.,
> the
> >>>>> binaries are signed with the duffy@indeed.com GPG key. For any final
> >>>>> release, I would be using hardware under personal control and a key
> >>>>> associated with cduffy@apache.org.
> >>>>
> >>>> Please make sure whatever key you use is inside
> >>>> https://dist.apache.org/repos/dist/release/ant/KEYS - if you need any
> >>>> help committing it there, please yell.
> >>>>
> >>>> Cheers
> >>>>
> >>>> Stefan
> >>>>
> >>>> ---------------------------------------------------------------------
> >>>> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
> >>>> For additional commands, e-mail: dev-help@ant.apache.org
> >>>>
> >>>>
> >>>
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
> > For additional commands, e-mail: dev-help@ant.apache.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
> For additional commands, e-mail: dev-help@ant.apache.org
>
>
Re: [VOTE] Ivy 2.4.0-rc1 Release
Posted by Nicolas Lalevée <ni...@hibnet.org>.
Le 22 janv. 2014 à 00:52, Nicolas Lalevée <ni...@hibnet.org> a écrit :
> I have found some issues. The source distribution seems to miss some test files. I guess this has been the case for quite some time. And it is "just" about the tests. And it is an RC. So OK for me. And I will fix that soon in trunk.
>
> To avoid confusion and make things simpler, I suggest we modify the release process to that everything goes through the svn of dist.apache.org, and not use anymore people.apache.org. In the end, everything is published there.
> And I'll modify in the doc of the release process the template of the email of the vote to include a line that is referencing the svn tag. So it's more difficult to miss it, and it is helpful to do review.
>
> I have tested the staging update site: works like a charm.
>
> So LGTM.
>
> I will cast my vote as soon as I can verify the signature of the artifacts.
You pushed some keys to the KEYS files, but it doesn't seems to be the same as the one you used to sign the proposed artifacts.
My gpg is asking for the key ID 93FB868A. Did I do something wrong or the keys are actually different ?
Nicolas
>
> Nicolas
>
> Le 21 janv. 2014 à 17:19, Charles Duffy <ch...@dyfis.net> a écrit :
>
>> FYI --
>>
>> A tag at https://svn.apache.org/repos/asf/ant/ivy/core/tags/2.4.0-rc1 now
>> exists. This differs from the branch head from which the binaries for test
>> were built only inasmuch as its svn:externals specify a specific revision
>> of the documentation build tools rather than leaving their revision
>> floating.
>>
>>
>> On Tue, Jan 21, 2014 at 6:54 AM, Charles Duffy <ch...@dyfis.net> wrote:
>>
>>> Howdy --
>>>
>>> I've attempted to follow the documentation at
>>> http://ant.apache.org/ivy/history/trunk/dev/makerelease.html and
>>> http://ant.apache.org/ivy/ivyde/history/trunk/dev/updatesite.html (as
>>> included-by-reference in the former) in preparing the above. That said, it
>>> appears that I missed step 12 (and, accordingly, have a 1.4.0-rc1 branch,
>>> from the present tip of which the binaries were built, but no associated
>>> tag).
>>>
>>> I'll be sure to get KEYS up-to-date. Thank you for the pointers.
>>>
>>>
>>> On Tue, Jan 21, 2014 at 6:26 AM, Stefan Bodewig <bo...@apache.org>wrote:
>>>
>>>> Hi Charles,
>>>>
>>>> we don't really release binaries, they are just a convenience. All that
>>>> matters as a release is the sources.
>>>>
>>>> I'm not sure there is anything documenting the release process for Ivy
>>>> but in general you create an svn tag and build source and binary
>>>> distributions from that.
>>>>
>>>> What you have built now is a binary for testing and you don't really
>>>> need to vote on that at all. Just encourage people to try it out :-)
>>>>
>>>> If you want to perform some sort of test-release, have a look at
>>>> <http://svn.apache.org/repos/asf/ant/antlibs/ReleaseInstructions> and
>>>> similar instructions to get an idea of what is expected.
>>>>
>>>>> PS -- As this build was performed on hardware owned by Indeed, Inc., the
>>>>> binaries are signed with the duffy@indeed.com GPG key. For any final
>>>>> release, I would be using hardware under personal control and a key
>>>>> associated with cduffy@apache.org.
>>>>
>>>> Please make sure whatever key you use is inside
>>>> https://dist.apache.org/repos/dist/release/ant/KEYS - if you need any
>>>> help committing it there, please yell.
>>>>
>>>> Cheers
>>>>
>>>> Stefan
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
>>>> For additional commands, e-mail: dev-help@ant.apache.org
>>>>
>>>>
>>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
> For additional commands, e-mail: dev-help@ant.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org
Re: [VOTE] Ivy 2.4.0-rc1 Release
Posted by Nicolas Lalevée <ni...@hibnet.org>.
Le 22 janv. 2014 à 06:27, Stefan Bodewig <bo...@apache.org> a écrit :
> On 2014-01-22, Nicolas Lalevée wrote:
>
>> To avoid confusion and make things simpler, I suggest we modify the
>> release process to that everything goes through the svn of
>> dist.apache.org, and not use anymore people.apache.org.
>
> +1
>
> we may need to adjust things if Charles cannot commit there - I vaguelly
> recall a thread in Commons where only PMC members had write access but
> changing that was only a matter of a JIRA ticket for infra.
He can, since the staging eclipse updatesite as already been pushed there. But maybe there are different rights between the dev and release spaces of dist.
Nicolas
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org
Re: [VOTE] Ivy 2.4.0-rc1 Release
Posted by Stefan Bodewig <bo...@apache.org>.
On 2014-01-22, Nicolas Lalevée wrote:
> To avoid confusion and make things simpler, I suggest we modify the
> release process to that everything goes through the svn of
> dist.apache.org, and not use anymore people.apache.org.
+1
we may need to adjust things if Charles cannot commit there - I vaguelly
recall a thread in Commons where only PMC members had write access but
changing that was only a matter of a JIRA ticket for infra.
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org
Re: [VOTE] Ivy 2.4.0-rc1 Release
Posted by Nicolas Lalevée <ni...@hibnet.org>.
I have found some issues. The source distribution seems to miss some test files. I guess this has been the case for quite some time. And it is "just" about the tests. And it is an RC. So OK for me. And I will fix that soon in trunk.
To avoid confusion and make things simpler, I suggest we modify the release process to that everything goes through the svn of dist.apache.org, and not use anymore people.apache.org. In the end, everything is published there.
And I'll modify in the doc of the release process the template of the email of the vote to include a line that is referencing the svn tag. So it's more difficult to miss it, and it is helpful to do review.
I have tested the staging update site: works like a charm.
So LGTM.
I will cast my vote as soon as I can verify the signature of the artifacts.
Nicolas
Le 21 janv. 2014 à 17:19, Charles Duffy <ch...@dyfis.net> a écrit :
> FYI --
>
> A tag at https://svn.apache.org/repos/asf/ant/ivy/core/tags/2.4.0-rc1 now
> exists. This differs from the branch head from which the binaries for test
> were built only inasmuch as its svn:externals specify a specific revision
> of the documentation build tools rather than leaving their revision
> floating.
>
>
> On Tue, Jan 21, 2014 at 6:54 AM, Charles Duffy <ch...@dyfis.net> wrote:
>
>> Howdy --
>>
>> I've attempted to follow the documentation at
>> http://ant.apache.org/ivy/history/trunk/dev/makerelease.html and
>> http://ant.apache.org/ivy/ivyde/history/trunk/dev/updatesite.html (as
>> included-by-reference in the former) in preparing the above. That said, it
>> appears that I missed step 12 (and, accordingly, have a 1.4.0-rc1 branch,
>> from the present tip of which the binaries were built, but no associated
>> tag).
>>
>> I'll be sure to get KEYS up-to-date. Thank you for the pointers.
>>
>>
>> On Tue, Jan 21, 2014 at 6:26 AM, Stefan Bodewig <bo...@apache.org>wrote:
>>
>>> Hi Charles,
>>>
>>> we don't really release binaries, they are just a convenience. All that
>>> matters as a release is the sources.
>>>
>>> I'm not sure there is anything documenting the release process for Ivy
>>> but in general you create an svn tag and build source and binary
>>> distributions from that.
>>>
>>> What you have built now is a binary for testing and you don't really
>>> need to vote on that at all. Just encourage people to try it out :-)
>>>
>>> If you want to perform some sort of test-release, have a look at
>>> <http://svn.apache.org/repos/asf/ant/antlibs/ReleaseInstructions> and
>>> similar instructions to get an idea of what is expected.
>>>
>>>> PS -- As this build was performed on hardware owned by Indeed, Inc., the
>>>> binaries are signed with the duffy@indeed.com GPG key. For any final
>>>> release, I would be using hardware under personal control and a key
>>>> associated with cduffy@apache.org.
>>>
>>> Please make sure whatever key you use is inside
>>> https://dist.apache.org/repos/dist/release/ant/KEYS - if you need any
>>> help committing it there, please yell.
>>>
>>> Cheers
>>>
>>> Stefan
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
>>> For additional commands, e-mail: dev-help@ant.apache.org
>>>
>>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org
Re: [VOTE] Ivy 2.4.0-rc1 Release
Posted by Charles Duffy <ch...@dyfis.net>.
FYI --
A tag at https://svn.apache.org/repos/asf/ant/ivy/core/tags/2.4.0-rc1 now
exists. This differs from the branch head from which the binaries for test
were built only inasmuch as its svn:externals specify a specific revision
of the documentation build tools rather than leaving their revision
floating.
On Tue, Jan 21, 2014 at 6:54 AM, Charles Duffy <ch...@dyfis.net> wrote:
> Howdy --
>
> I've attempted to follow the documentation at
> http://ant.apache.org/ivy/history/trunk/dev/makerelease.html and
> http://ant.apache.org/ivy/ivyde/history/trunk/dev/updatesite.html (as
> included-by-reference in the former) in preparing the above. That said, it
> appears that I missed step 12 (and, accordingly, have a 1.4.0-rc1 branch,
> from the present tip of which the binaries were built, but no associated
> tag).
>
> I'll be sure to get KEYS up-to-date. Thank you for the pointers.
>
>
> On Tue, Jan 21, 2014 at 6:26 AM, Stefan Bodewig <bo...@apache.org>wrote:
>
>> Hi Charles,
>>
>> we don't really release binaries, they are just a convenience. All that
>> matters as a release is the sources.
>>
>> I'm not sure there is anything documenting the release process for Ivy
>> but in general you create an svn tag and build source and binary
>> distributions from that.
>>
>> What you have built now is a binary for testing and you don't really
>> need to vote on that at all. Just encourage people to try it out :-)
>>
>> If you want to perform some sort of test-release, have a look at
>> <http://svn.apache.org/repos/asf/ant/antlibs/ReleaseInstructions> and
>> similar instructions to get an idea of what is expected.
>>
>> > PS -- As this build was performed on hardware owned by Indeed, Inc., the
>> > binaries are signed with the duffy@indeed.com GPG key. For any final
>> > release, I would be using hardware under personal control and a key
>> > associated with cduffy@apache.org.
>>
>> Please make sure whatever key you use is inside
>> https://dist.apache.org/repos/dist/release/ant/KEYS - if you need any
>> help committing it there, please yell.
>>
>> Cheers
>>
>> Stefan
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
>> For additional commands, e-mail: dev-help@ant.apache.org
>>
>>
>
Re: [VOTE] Ivy 2.4.0-rc1 Release
Posted by Charles Duffy <ch...@dyfis.net>.
Howdy --
I've attempted to follow the documentation at
http://ant.apache.org/ivy/history/trunk/dev/makerelease.html and
http://ant.apache.org/ivy/ivyde/history/trunk/dev/updatesite.html (as
included-by-reference in the former) in preparing the above. That said, it
appears that I missed step 12 (and, accordingly, have a 1.4.0-rc1 branch,
from the present tip of which the binaries were built, but no associated
tag).
I'll be sure to get KEYS up-to-date. Thank you for the pointers.
On Tue, Jan 21, 2014 at 6:26 AM, Stefan Bodewig <bo...@apache.org> wrote:
> Hi Charles,
>
> we don't really release binaries, they are just a convenience. All that
> matters as a release is the sources.
>
> I'm not sure there is anything documenting the release process for Ivy
> but in general you create an svn tag and build source and binary
> distributions from that.
>
> What you have built now is a binary for testing and you don't really
> need to vote on that at all. Just encourage people to try it out :-)
>
> If you want to perform some sort of test-release, have a look at
> <http://svn.apache.org/repos/asf/ant/antlibs/ReleaseInstructions> and
> similar instructions to get an idea of what is expected.
>
> > PS -- As this build was performed on hardware owned by Indeed, Inc., the
> > binaries are signed with the duffy@indeed.com GPG key. For any final
> > release, I would be using hardware under personal control and a key
> > associated with cduffy@apache.org.
>
> Please make sure whatever key you use is inside
> https://dist.apache.org/repos/dist/release/ant/KEYS - if you need any
> help committing it there, please yell.
>
> Cheers
>
> Stefan
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
> For additional commands, e-mail: dev-help@ant.apache.org
>
>
Re: [VOTE] Ivy 2.4.0-rc1 Release
Posted by Stefan Bodewig <bo...@apache.org>.
Hi Charles,
we don't really release binaries, they are just a convenience. All that
matters as a release is the sources.
I'm not sure there is anything documenting the release process for Ivy
but in general you create an svn tag and build source and binary
distributions from that.
What you have built now is a binary for testing and you don't really
need to vote on that at all. Just encourage people to try it out :-)
If you want to perform some sort of test-release, have a look at
<http://svn.apache.org/repos/asf/ant/antlibs/ReleaseInstructions> and
similar instructions to get an idea of what is expected.
> PS -- As this build was performed on hardware owned by Indeed, Inc., the
> binaries are signed with the duffy@indeed.com GPG key. For any final
> release, I would be using hardware under personal control and a key
> associated with cduffy@apache.org.
Please make sure whatever key you use is inside
https://dist.apache.org/repos/dist/release/ant/KEYS - if you need any
help committing it there, please yell.
Cheers
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org
Re: [VOTE] Ivy 2.4.0-rc1 Release
Posted by Jean-Louis Boudart <je...@gmail.com>.
+1
2014/1/21 Per Arnold Blaasmo <pe...@atmel.com>
> +1
>
>
> On 20. jan. 2014 19:19, Charles Duffy wrote:
> > I have built a release candidate for Ivy 2.4.0.
> >
> > You can download it from this URL:
> > http://people.apache.org/~cduffy/ivy-2.4.0-rc1/
> >
> > Do you vote for the release of these binaries?
> >
> > [ ] Yes
> > [ ] No
> >
> > Regards,
> >
> > Charles Duffy, Ivy 2.4.0 release manager
> >
> >
> > PS -- As this build was performed on hardware owned by Indeed, Inc., the
> > binaries are signed with the duffy@indeed.com GPG key. For any final
> > release, I would be using hardware under personal control and a key
> > associated with cduffy@apache.org.
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
> For additional commands, e-mail: dev-help@ant.apache.org
>
>
--
Jean Louis Boudart
Independent consultant
Apache EasyAnt commiter http://ant.apache.org/easyant/
Re: [VOTE] Ivy 2.4.0-rc1 Release
Posted by Per Arnold Blaasmo <pe...@atmel.com>.
+1
On 20. jan. 2014 19:19, Charles Duffy wrote:
> I have built a release candidate for Ivy 2.4.0.
>
> You can download it from this URL:
> http://people.apache.org/~cduffy/ivy-2.4.0-rc1/
>
> Do you vote for the release of these binaries?
>
> [ ] Yes
> [ ] No
>
> Regards,
>
> Charles Duffy, Ivy 2.4.0 release manager
>
>
> PS -- As this build was performed on hardware owned by Indeed, Inc., the
> binaries are signed with the duffy@indeed.com GPG key. For any final
> release, I would be using hardware under personal control and a key
> associated with cduffy@apache.org.
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org