ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nicolas Lalevée <>
Subject Re: [VOTE] Ivy 2.4.0-rc1 Release
Date Tue, 21 Jan 2014 23:52:27 GMT
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, and not use anymore
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.


I will cast my vote as soon as I can verify the signature of the artifacts.


Le 21 janv. 2014 à 17:19, Charles Duffy <> a écrit :

> FYI --
> A tag at 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 <> wrote:
>> Howdy --
>> I've attempted to follow the documentation at
>> and
>> (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 <>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
>>> <> 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 GPG key. For any final
>>>> release, I would be using hardware under personal control and a key
>>>> associated with
>>> Please make sure whatever key you use is inside
>>> - if you need any
>>> help committing it there, please yell.
>>> Cheers
>>>        Stefan
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail:
>>> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message