Mailing-List: contact dev-help@tiles.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@tiles.apache.org
Received-SPF: pass (herse.apache.org: domain of antonio.petrelli@gmail.com
 designates 64.233.166.177 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=Ik6Q5d0wQQiidKPeSZG9T6ZbdKOs1/vkX4p0agdIuhlqueMxC1d7u1ZFub2QT53gezB7y+FP/e+cF1LZKxD0A62sR8ySIGAhpJwioKEqfHStcXmhrFwsjo6d/pVudkqP/FG5JHekAgGX4YTCLBC3a3TYoa8uqCm6p5U98hBVEgY=
Message-ID: <aae96ca0703300800j4698b536g63eb6a35276af839@mail.gmail.com>
Date: Fri, 30 Mar 2007 17:00:56 +0200
From: "Antonio Petrelli" <antonio.petrelli@gmail.com>
To: dev@tiles.apache.org
Subject: Re: Missing License headers in 2.0.2 release
In-Reply-To: <4d651da50703300754o52bf274ci10ca4754299f27ed@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <aae96ca0703300544u370d7a1epc83e1f301c7eadb7@mail.gmail.com>
	 <91478db0703300718t23599007sb532470516d2d7ef@mail.gmail.com>
	 <aae96ca0703300722pbd734pad101677460496c5@mail.gmail.com>
	 <460D1E0F.6030701@apache.org>
	 <4d651da50703300754o52bf274ci10ca4754299f27ed@mail.gmail.com>

2007/3/30, Nathan Bubna <nbubna@gmail.com>:
> But have we actually put out a 2.0.2 build to be tested and voted on?
> If not, i see no problem with moving the 2.0.2 tag.

Mmm I think it's better to list the pros and cons of each approach.
- Stick with 2.0.2:
Pros: The release version remains the same.
Cons: It means that we have to change the trunk back, remove the 2.0.2
tag, remove the JIRA version, move the JIRA issue to 2.0.2. And, last
but not least, it seems not-so-legal to me :-)

- Go ahead to 2.0.3
Pros: it's easy to do.
Cons: there will be a  "hole" in version sequence.

I solved some problems that I noticed only during the release of
2.0.2. From my POV the "new tag" approach is the best (I am making the
release, so it is in my interest :-) ) but I am open to comments.

Antonio