Some little notes about that last release:
* in the tag, the svn:external to xooki was not changed to a fixed revision (it is in the release doc just after tagging the release branch)
* in the staging updatesite there was Ivy 2.1, IvyDE 2.0 and IvyDE 2.1, but not Ivy 2.0 (the point of IVYDE-185 was to have Ivy 2.0 there)
* it would be cool if for each Ivy released jar, the Ivy Ant plugin could be generated too (related to IVYDE-171). I think it will be quite simple, just run for both Ivy jars in the updatesite:
ant install-ivy -Divy.jar=dist/plugins/org.apache.ivy_2.........jar

I also took some little time to run it, and it was working great. :)

About your gpg public key, did you put it in a particular place ? I am not able to find it. You will probably also want to export into that KEYS file:
https://svn.apache.org/repos/asf/ant/core/trunk/KEYS
see the beginning of that file to know how to proceed.

cheers,
Nicolas

Le 4 févr. 2010 à 14:08, Jon Schneider a écrit :

> The RC was just a guess on my part. If we are going straight to a final
> version, I'll rebuild and update my staging site.
>
> Jon
>
> 2010/2/4 Nicolas Lalevée <nicolas.lalevee@(protected)>
>
>> On Wed, 3 Feb 2010 19:24:22 -0600, Jon Schneider <jkschneider@(protected)>
>> wrote:
>>> It is meant to be an RC1.
>>
>> I am a bit confused too. We didn't talked about doing a RC, just a 2.1.0,
>> a final one.
>> Do you want to do an RC ? I am confident in the stability of the current
>> code, I am fine with going out without RC. And if there are some major bugs
>> found quickly, we could roll out quickly too a 2.1.1.
>>
>> Nicolas
>>
>>
>>>
>>> Thanks,
>>>
>>> Jon
>>>
>>> On Wed, Feb 3, 2010 at 3:38 PM, Maarten Coene
>>> <maarten_coene@(protected):
>>>
>>>> Jon,
>>>>
>>>> I'm a bit confused. Did you build a IvyDE 2.1.0-RC1, or did you build
>>>> IvyDE
>>>> 2.1.0 final?
>>>>
>>>> I have some questions/remarks:
>>>> - the binary distribution files don't have a seperate doc folder (like
>>>> the
>>>> ivyde-2.0 binary distributions), the documentation structure starts
>>>> directly
>>>> at the root
>>>> - what is the purpose of the file 'version.properties' in your
>>>> ivyde-2.1.0
>>>> directory?
>>>>
>>>> If you did build the IvyDE 2.1.0-final:
>>>> - the version of the ivyde plugin on the update site doesn't has a
>>>> "final"
>>>> in it's name (which was the case with previous ivyde releases). If I'm
>>>> not
>>>> mistaken there was a reason to include this "final" in the version, but
>> I
>>>> can't remember what is was.
>>>>
>>>>
>>>> There is no need to announce this to the ivy-user list before there has
>>>> been a vote on this list ...
>>>>
>>>> Maarten
>>>>
>>>>
>>>>
>>>> ----- Original Message ----
>>>> From: Jon Schneider <jschneider@(protected)>
>>>> To: Ant Developers List <dev@(protected)>
>>>> Sent: Wed, February 3, 2010 3:41:14 PM
>>>> Subject: IvyDE 2.1.0 Release
>>>>
>>>> I have built a release candidate for IvyDE 2.1.0. You can download the
>>>> distribution at [1]. A staging updatesite has been deployed at [2].
>>>>
>>>> I went through the whole set of documentation and corrected spelling
>> and
>>>> grammar and made a few clarifying points here and there.
>>>>
>>>> I've signed the artifacts, but seeing as I'm kind of new here, nobody
>>>> else
>>>> has signed my key. I'm not sure how picky folks will be about this.
>> If
>>>> it
>>>> will be a problem, somebody else can sign it before the deployment of
>> the
>>>> final build. Should we announce the release candidate on ivy-user
>> prior
>>>> to
>>>> a vote on the final release?
>>>>
>>>> Thanks,
>>>> Jon
>>>>
>>>> [1] http://people.apache.org/~jschneider/ivyde-2.1.0/
>>>> [2] http://people.apache.org/~jschneider/staging/updatesite/
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@(protected)
>>>> For additional commands, e-mail: dev-help@(protected)
>>>>
>>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@(protected)
>> For additional commands, e-mail: dev-help@(protected)
>>
>>


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@(protected)
For additional commands, e-mail: dev-help@(protected)