Nope, you're not confused.  It looks like the tag didn't get created properly 
from the branch.

Thanks for taking a quick look.  Will be addressed in just a bit.

-N



----- Original Message ----
From: Kevan Miller <[email protected]>
To: [email protected]
Sent: Mon, November 2, 2009 9:40:46 AM
Subject: Re: [VOTE] Release Wink 1.0 (RC-4)

I'm confused. I like the license/notice files in trunk and branches/1.0 (e.g. 
https://svn.apache.org/repos/asf/incubator/wink/branches/1.0-incubating/NOTICE)

I don't like the license/notice files in the tag 
(https://svn.apache.org/repos/asf/incubator/wink/tags/wink-1.0-incubating/NOTICE)
 or the source distribution file that you just put up for a vote.

Unless I'm totally confused, here's my -1.

A few additional notes:

the attributions to AL2 licensed projects in the NOTICE file (e.g. "This 
product includes software, StAX API (http://stax.codehaus.org/) distributed 
under Apache-2.0 license") are not necessary, unless the jar files contain a 
NOTICE (and the notice is not for the ASF).

wink-1.0-incubating is in svn twice -- 
https://svn.apache.org/repos/asf/incubator/wink/tags/wink-1.0-incubating/ and 
https://svn.apache.org/repos/asf/incubator/wink/tags/wink-1.0-incubating/wink-1.0-incubating/

if a vote is cancelled, please note this by sending a [CANCELLED][VOTE] email. 
The updated subject makes it easier to track... Doesn't look like this has 
happened for some of the previous votes.

--kevan


On Nov 1, 2009, at 9:39 PM, Nicholas Gallardo wrote:

> I'm calling a vote to release Wink 0.1
> 
> The Maven staging area is at:
> https://repository.apache.org/content/repositories/orgapachewink-008/
> 
> The distributions are in:
> https://repository.apache.org/content/repositories/orgapachewink-008/org/apache/wink/apache-wink/1.0-incubating/
> 
> This release is tagged at:
> https://svn.apache.org/repos/asf/incubator/wink/tags/wink-0.1-incubating/  
> (revision 831791)
> 
> The vote will be open here for at least 72 hours.
> 
> Consider this my +1
> 
> 
> 
> 


      

Reply via email to