Cool.  I'll proceed with pushing out 1.1.0 and go from there!

Elliot

Sent from webmail (apologies for the poor quoting)
>>> "David H. DeWolf" <[EMAIL PROTECTED]> 02/21/07 6:46 PM >>>
No, what's done is done.  We should leave 1.1.0 alone - but note the 
issue, and work to cut a 1.1.1 release asap.  Now that the build process

has been streamlined, I don't mind cutting them regularly.  In fact, I'd

love to have a goal of one per month.

Let's give this release a couple of weeks of bug reports and fixes and 
then push out another.  If someone needs a 1.4 version and speaks up 
about it, then we can cut one immediately and do 1.1.2 afterwards.


David

Elliot Metsger wrote:
> Today, despite all our testing efforts, I found 1.5 code in the 1.1.0 
> test release.  https://issues.apache.org/jira/browse/PLUTO-313 has the

> details of the class involved.
> 
> After patching, do we move forward with another vote?  I know I'm not 
> up-to-speed on the procedural requirements: if we need to vote for the

> release again?
> 
> Elliot
> 

Reply via email to