Kevan, 
Thank a lot for your insight. Will apply your recommendations in an upcoming 
RC.  

Regards 
--martin

-----Original Message-----
From: Kevan Miller [mailto:[email protected]] 
Sent: Friday, August 14, 2009 7:55 PM
To: [email protected]
Subject: Re: [VOTE] Release Wink 0.1


On Aug 5, 2009, at 4:01 AM, Snitkovsky, Martin wrote:

> Folks,
>
> I'm calling a vote to release Wink 0.1
>
> The Maven staging area is at:
> https://repository.apache.org/content/repositories/wink-staging-014/
>
> The distributions are in:
> https://repository.apache.org/content/repositories/wink-staging-014/org/apache/wink/apache-wink/0.1-incubating/
>
> This release is tagged at:
> https://svn.apache.org/repos/asf/incubator/wink/tags/wink-0.1-incubating/
>
> The vote will be open here for at least 72 hours.
>
> Please consider this call to vote as my +1

Martin,
It's a good idea to explicitly record when a vote has been stopped or  
cancelled. This can be a big help when your search back through an  
email list...

Projects can decide how, exactly, they might want to do this. One  
common method is to post a reply to this email thread with a new  
subject. Something like:

*************************************************
Subject: [CANCELLED][VOTE] Release Wink 0.1

Due to the problems found in this release (e.g. LICENSE and NOTICE  
file issues), the vote is cancelled. Will be fixing these issues and  
generate a new release candidate. In the meantime, please let me know  
if any further problems are uncovered with this release.

*************************************************

Since you called the vote, this would typically be expected to be your  
responsibility.

Also, I'd recommend you uniquely name vote threads. Something like:

[VOTE] Release Wink 0.1 (RC1)

The naming (e.g. RC1) is simply a name that you're applying to the  
vote thread. Not something that needs to be reflected in the artifact  
names or svn tags.

Note that this is in no way intended to be a *criticism*. Just passing  
along institutional knowledge...

--kevan 

Reply via email to