Mailing-List: contact dev-help@ant.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Ant Developers List" <dev@ant.apache.org>
Received-SPF: pass (nike.apache.org: domain of jak-ant-dev@m.gmane.org
 designates 80.91.229.3 as permitted sender)
To: dev@ant.apache.org
From: Jesse Glick <jesse.glick@oracle.com>
Subject: Re: Merging to the 1.8.x branch
Date: Mon, 19 Mar 2012 13:15:18 -0400
Organization: Oracle Corp. / NetBeans
Lines: 7
Message-ID: <jk7pj7$gqr$1@dough.gmane.org>
References: <87d38ddtvx.fsf@v35516.1blu.de>
 <CAE9L6G1pNKgfJ+SvjtLChBVh9e57KkOrc2agTtkYyDV0FBfpKQ@mail.gmail.com>
 <4F63A738.4010502@callenish.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
 rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
In-Reply-To: <4F63A738.4010502@callenish.com>

On 03/16/2012 04:48 PM, Bruce Atherton wrote:
> If there are bug fixes that need to go into a future 1.8.4 release we can deal with them when the time comes.

Agreed, i.e. option 2. Rather than sifting through all commits made into trunk - which besides Java 5 could include all sorts of code cleanups or other minor stuff - 
looking to see what might be applicable to 1.8.x, I think it would make more sense to keep the 1.8.x branch relatively frozen. If and when we decide to do a 1.8.4 
release, we can look through Bugzilla for fixed bugs with TM >= 1.9.0, decide which ones are good backport candidates (important bug, safe and well-tested fix), and merge 
or otherwise backport just the necessary bug fix commits.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org