Propose 1.7.2 Bugfix Release

[Adam Batkin <ad...@batkin.net>]

Hi,

I would like to propose that there be a 1.7.2 Bugfix Only release.

In particular, I am interested in bug 43114:
https://issues.apache.org/bugzilla/show_bug.cgi?id=43114
Though I am sure that other people have their own pet bugs that they 
feel are absolutely critical and should be included too.

I am also willing to contribute my time toward putting the release 
together, since from what I have read, that may be one of the biggest 
things holding this back.

Thoughts? Where do we go from here? What can I do to help?

-Adam Batkin

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

Re: Propose 1.7.2 Bugfix Release

[Stefan Bodewig <bo...@apache.org>]

On 2009-11-25, Adam Batkin <ad...@batkin.net> wrote:

> So if people on this list think that 1.8.0 will come out in a
> reasonable timeframe (and/or at least seriously discuss a timeframe so
> that people looking for critical fixes can plan appropriately) then I
> can wait until then.

I hope and believe this is the case.

> Otherwise I'd be interested in branching from 1.7.1, picking a bunch
> of bugs and merging in those patches. I think the criteria for fixes
> would have to be something like:
> - Someone cares enough about the particular issue that they say that
> it should be specifically included

This would probably be the most difficult part.  Wading through the
bugzilla list of fixed issues will take almost as long as creating the
release 8-)

> - Fix is reasonably easy to merge in (i.e. doesn't depend on some
> major structural change for 1.8.0)

Many will have been refactored later.

> - Fix is backwards compatible (except in cases where backwards
> compatible means "totally broken")

There shouldn't be any change in Ant trunk (except for the new
PropertyHelper API) that wouldn't qualify.

Stefan

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

Re: Propose 1.7.2 Bugfix Release

[Stefan Bodewig <bo...@apache.org>]

On 2009-11-30, Antoine Levy Lambert <an...@gmx.de> wrote:

> I volunteer to be a release manager for 1.8.0, or maybe co-release
> manager with Stefan.

Thank you Antoine.  I'll be traveling for the next few days but it looks
as if I could start breathing after that again, so I would hope to be
able to start the release process soon.  Given your experience in
releasing Ant, your help will be much apreciated.

Like I said, I think there is some documentation missing (target-group)
and I wouldn't want to release Ant without that.  Then again I'd skip
the alpha phase completely since alphas don't get tested anyway, I'd
prefer to go to release candidate immediately and plan for a 1.8.1 in a
two or three months.

Stefan

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

Re: Propose 1.7.2 Bugfix Release

[Antoine Levy Lambert <an...@gmx.de>]

Hi,

I am an ant committer who has not been very active lately :(.

I volunteer to be a release manager for 1.8.0, or maybe co-release 
manager with Stefan.

I do not know what is in the box currently and how mature we are. I 
guess that if the other committers agree I could make a first alpha 
release in the next days. I would have to dive again into 
"ReleaseInstructions".

Regards,

Antoine

Adam Batkin wrote:
> On 11/24/2009 05:10 AM, Stefan Bodewig wrote:
>> On 2009-11-23, Jesse Glick<je...@sun.com>  wrote:
>>
>>> I'm not sure backporting bug fixes is worth the effort when there is
>>> nothing in particular holding up a 1.8.0 release that I know of.
>>
>> Time, but that applies to any release.
>>
>> I am planning to volunteer as release manager for 1.8.0 by the end of
>> the year - I had hoped to get to it earlier than that but real life got
>> into the way.
>>
>> FWIW I wouldn't object a 1.7.2 release but completely lack the time to
>> support it.
>>
>>  From my POV the only things missing for a 1.8.0 release are proper
>> documentation of target-group and better documentation on the include
>> (and its difference WRT import) task.  No biggies.  I do have some
>> concerns because of the exec unit tests failures.
>
> So if people on this list think that 1.8.0 will come out in a 
> reasonable timeframe (and/or at least seriously discuss a timeframe so 
> that people looking for critical fixes can plan appropriately) then I 
> can wait until then.
>
> Otherwise I'd be interested in branching from 1.7.1, picking a bunch 
> of bugs and merging in those patches. I think the criteria for fixes 
> would have to be something like:
> - Someone cares enough about the particular issue that they say that 
> it should be specifically included
> - Fix already exists
> - Fix is reasonably easy to merge in (i.e. doesn't depend on some 
> major structural change for 1.8.0)
> - Fix is backwards compatible (except in cases where backwards 
> compatible means "totally broken")
>
> I would be willing to take a stab at it. I'm not an Ant committer (and 
> don't expect to be made one any time soon, given that I just "walked 
> in off the street" and you have no idea who I am) so we'd need to 
> figure out something from a technical perspective. Perhaps I could 
> create a local Mercurial clone of the repository and push changes to 
> that, so that each commit could be viewed individually (rather than a 
> gigantic patch at the end).
>
> Thanks,
>
> -Adam Batkin
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
> For additional commands, e-mail: dev-help@ant.apache.org


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

Re: Propose 1.7.2 Bugfix Release

[Adam Batkin <ad...@batkin.net>]

On 11/24/2009 05:10 AM, Stefan Bodewig wrote:
> On 2009-11-23, Jesse Glick<je...@sun.com>  wrote:
>
>> I'm not sure backporting bug fixes is worth the effort when there is
>> nothing in particular holding up a 1.8.0 release that I know of.
>
> Time, but that applies to any release.
>
> I am planning to volunteer as release manager for 1.8.0 by the end of
> the year - I had hoped to get to it earlier than that but real life got
> into the way.
>
> FWIW I wouldn't object a 1.7.2 release but completely lack the time to
> support it.
>
>  From my POV the only things missing for a 1.8.0 release are proper
> documentation of target-group and better documentation on the include
> (and its difference WRT import) task.  No biggies.  I do have some
> concerns because of the exec unit tests failures.

So if people on this list think that 1.8.0 will come out in a reasonable 
timeframe (and/or at least seriously discuss a timeframe so that people 
looking for critical fixes can plan appropriately) then I can wait until 
then.

Otherwise I'd be interested in branching from 1.7.1, picking a bunch of 
bugs and merging in those patches. I think the criteria for fixes would 
have to be something like:
- Someone cares enough about the particular issue that they say that it 
should be specifically included
- Fix already exists
- Fix is reasonably easy to merge in (i.e. doesn't depend on some major 
structural change for 1.8.0)
- Fix is backwards compatible (except in cases where backwards 
compatible means "totally broken")

I would be willing to take a stab at it. I'm not an Ant committer (and 
don't expect to be made one any time soon, given that I just "walked in 
off the street" and you have no idea who I am) so we'd need to figure 
out something from a technical perspective. Perhaps I could create a 
local Mercurial clone of the repository and push changes to that, so 
that each commit could be viewed individually (rather than a gigantic 
patch at the end).

Thanks,

-Adam Batkin

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

Re: Propose 1.7.2 Bugfix Release

[Stefan Bodewig <bo...@apache.org>]

On 2009-11-23, Jesse Glick <je...@sun.com> wrote:

> I'm not sure backporting bug fixes is worth the effort when there is
> nothing in particular holding up a 1.8.0 release that I know of.

Time, but that applies to any release.

I am planning to volunteer as release manager for 1.8.0 by the end of
the year - I had hoped to get to it earlier than that but real life got
into the way.

FWIW I wouldn't object a 1.7.2 release but completely lack the time to
support it.

>From my POV the only things missing for a 1.8.0 release are proper
documentation of target-group and better documentation on the include
(and its difference WRT import) task.  No biggies.  I do have some
concerns because of the exec unit tests failures.

Stefan

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

Re: Propose 1.7.2 Bugfix Release

[Jesse Glick <je...@sun.com>]

Adam Batkin wrote:
> I am sure that other people have their own pet bugs that they 
> feel are absolutely critical and should be included too.

Candidates would be from among:

https://issues.apache.org/bugzilla/buglist.cgi?order=Importance&bug_severity=blocker&bug_severity=critical&bug_severity=regression&bug_severity=major&bug_severity=normal&bug_severity=minor&bug_severity=trivial&resolution=FIXED&query_format=advanced&bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&target_milestone=1.8.0&product=Ant

after filtering out bugs only introduced by changes in dev sources.

I'm not sure backporting bug fixes is worth the effort when there is nothing in particular holding up a 1.8.0 release that I know of. To quote Stefan from three months ago:

"I really wouldn't want to go through the pain of merging the bug fixes into the 1.7 branch (I have been willing to do so about a year ago [...] but we have changed too 
much in trunk after that)."

Of course if only a handful of "absolutely critical" bugs would be considered for 1.7.2 then the backporting may not be much work.


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