I agree. Option 2 is the better choice.
Changesets on trunk can be Java5 specific. It would be problematic to
have to also include tested Java 1.4 versions on a 1.8 branch that may
never see the light of day. 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. And
anyone who wants to do the extra work up front can do as you did,
updating that wiki page with the changeset that should be included (or
possibly including a 1.8.x patch in bugzilla if it is very different
from the change in trunk).
On 3/16/2012 8:09 AM, Matt Benson wrote:
On Thu, Mar 15, 2012 at 11:58 PM, Stefan Bodewig<bode...@apache.org> wrote:
Hi,
WRT merging to the branch we basically have two options: (1) merge when
we commit to trunk or (2) merge when we know we want to create another
1.8.x release.
I'm leaning towards (2) since I personally don't expect a 1.8.4
release. But just in case I've created a wiki page at
<http://wiki.apache.org/ant/MergeCandidates18xBranch> listing the
changesets that could be merged easily and would be important enough to
go into the next release. I haven't found the time to review Jesse's
commits of the past two weeks, yet.
Is this a dumb idea? Should we merge stuff right away?
Option 2 sounds fine to me.
Matt
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org
