Author Login
Post Reply
I have found some errors that I have fixed:
* the tag of the release was done in the old tag
* the Ivy feature jar in the update site was referencing some Ivy Ant Eclipse which wasn't there
Then it is good for me to launch a vote for a release !
Just a note on your GPG key Jon. It seems you have a "short" key. The ASF is recommending having a "longer" one. So if your currently checked in key has not actually been used publicly, I recommend you to make a new one to avoid the pain of having to deal with some transition process. You might be interested by this doc:
http://www.apache.org/dev/openpgp.html#generate-key
cheers,
Nicolas
Le 12 févr. 2010 à 17:22, Jon Schneider a écrit :
> Sorry, I neglected to add the URLs referenced in my last email:
>
> [1] http://people.apache.org/~jschneider/ivyde-2.1.0/
> [2] http://people.apache.org/~jschneider/staging/updatesite/
>
> Also, in case anybody notices, I have not merged changes the fixes I have
> made on the 2.1.0 branch back to trunk, but will do so selectively whenever
> the dust settles and we actually release it.
>
> Thanks,
> Jon
>
> On Fri, Feb 12, 2010 at 10:20 AM, Jon Schneider <jkschneider@(protected):
>
>> I have built a final candidate for IvyDE 2.1.0. You can download the
>> distribution at [1]. A staging updatesite has been deployed at [2]. I have
>> taken the following actions since the last build:
>>
>> 1. Rebuilt with the "final" version qualifier.
>> 2. Added my pub key to the KEYS file (thanks Nicholas).
>> 3. Added Ivy 2.0 to the updatesite.
>> 4. Ran the optimizer against Ivy and IvyDE on the updatesite with Matt's
>> fix so that the feature jars are packed too.
>> 5. Updated the signIvyArtifacts and signIvyDEArtifacts scripts to include
>> the new packed feature jars as well.
>> 6. Fixed build.xml in the ivyde 2.1.0 branch so that the documentation is
>> put in a doc directory in the distribution archives rather than at the root
>> (thanks Maarten).
>> 7. I deleted version.properties from my temporary distribution directory
>> to eliminate confusion.
>>
>> Did I miss anything?
>>
>> Like last time, I will wait a bit for feedback (if there is any) before
>> starting a vote on the release.
>>
>> Jon
>>
>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@(protected)
For additional commands, e-mail: dev-help@(protected)