ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Cohen" <>
Subject RE: Release schedule
Date Mon, 18 Nov 2002 14:55:51 GMT
Perhaps there ought to be a status with non-committing developers can
mark a bug to indicate that they have SUBMITTED a patch to fix it.

I was subconsciously using the same rules that we use in my organization
- developer's fix is indicated with "fixed" status.  It still must be
marked by someone else "verified fixed", before it is "closed".  Here,
though, there's only "fixed" and "closed".

-----Original Message-----
From: Stefan Bodewig [] 
Sent: Monday, November 18, 2002 1:56 AM
Subject: Re: Release schedule

On Sun, 17 Nov 2002, Steve Cohen <> wrote:

> Can someone tell me the plans for the next release (1.6?) of ant?

I'm with Steve here.  Some time next year.

> Also, I have an outstanding patch 
> (, that has 
> not been committed to the source tree.  Is there something I can do to

> improve its chances of getting into the next release?

Yes, don't mark it as fixed!

It simply dropped of my radar (and I guess this is true for moct
committers) as I run "Named Queries" for unresolved reports.  If
something has been resolved fixed, I'll never look at it except when
searching for "Duplicate" references.


To unsubscribe, e-mail:
For additional commands, e-mail:

To unsubscribe, e-mail:   <>
For additional commands, e-mail: <>

View raw message