Hi folks,
I have started to arrange stuff toward the release, and this is what we have:
* I have modified our Hudson build process. Now it generates and unloads to
Maven repo 2 archives - Wink sources and Wink binaries. Both will be part of
the release.
a. Sources uploaded to
https://repository.apache.org/content/repositories/snapshots/org/apache/wink/wink/0.1-incubating-SNAPSHOT/
b. Binaries uploaded to
https://repository.apache.org/content/repositories/snapshots/org/apache/wink/wink-dist/0.1-incubating-SNAPSHOT/
*NOTE*: Both are compressed as zip & tar.gz and uploaded to Maven repo
along with MD5 & SHA-1 checksums.
* DISCLAIMER.txt , LICENSE.txt, NOTICE.txt are archived along with sources and
binaries
Please download both archives and let me know if you have comments.
To be completed:
* Still have 5 open issues in JIRA
* Dims/Kevan, did not see an answer for Nik's question, regarding RC - "do
incubator projects publish release candidates?"
* Signing Release
(http://incubator.apache.org/guides/releasemanagement.html#notes-signing-releases)
* Release Notes
(http://incubator.apache.org/guides/releasemanagement.html#release-notes)
* Getting started. This is something that Nick mentioned - "some content on the
wiki with specific examples for how to take the build output, and package it up
into a WAR")
Pls let me know if I missed something.
Regards,
Martin
-----Original Message-----
From: Jason Dillon [mailto:[email protected]]
Sent: Tuesday, July 21, 2009 10:32 AM
To: [email protected]
Cc: [email protected]
Subject: Re: Wink 0.1 release
I can do it once I get a net connection. I've got >750 unread emails
ATM. Trying to cherry pick the over edge with my iPhone. Hope to get
online proper very soon.
--jason
On Jul 21, 2009, at 5:17 AM, Bryant Luk <[email protected]> wrote:
> Jason,
>
> Did you want to be (and have the time to be) the release manager for
> the 0.1 release? I don't recall seeing any e-mail/JIRA comment saying
> "yea" or "nay". I think Dims nominated you to be the release manager
> for 0.1 since you are one of the more experienced Apache committers.
> If not, no worries.
>
> On Wed, Jul 15, 2009 at 11:12 PM, Jason Dillon<[email protected]>
> wrote:
>> On Jul 15, 2009, at 9:55 PM, Baram, Eliezer wrote:
>>>
>>> OK, I thought that "fix version/s" is the field to fill after an
>>> issue is
>>> fixed to identify in which versions it was fixed.
>>> But if this the convention, fine with me.
>>
>> It is actually used for both. When the issue is not resolved it
>> means its
>> targeted for fix in that version, when the issue is resolved, then
>> it is
>> fixed in that version.
>>
>> --jason
>>
>>
>
>
>
> --
>
> - Bryant Luk
