You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@harmony.apache.org by Mark Hindess <ma...@googlemail.com> on 2009/11/03 22:36:29 UTC

[general] Milestone 12 proposed dates

We are due another milestone build at the end of the month.  I think we
should consider the following dates:

  Feature freeze  Fri 13th November
  Code freeze     Fri 20st November
  Publish         Fri 27th November

We should track issues that must be fixed for 5.0M12 with JIRA using the
"Fix for" field.  There is currently one issues marked this way and
I guess we should try to fix it.  To see the list visit the Harmony
JIRA homepage at:

  http://issues.apache.org/jira/browse/HARMONY

and click on "5.0M12" entry in the Versions column.

Should we try to do "6.0M1" a week later?  (This slightly complicates the
code freeze/thaw(?) but it spreads the work out a bit.)

Regards,
 Mark.



Re: [general] Milestone 12 proposed dates

Posted by Tim Ellison <t....@gmail.com>.
Reminder that we are now in code freeze for M12.

That means:
 - we switch to a review then commit model, any patches need approval
from another committer before going in, and
 - the only changes that can go in are to fix bugs that inhibit
declaration of our milestone by the end of the week.

Please take a moment to run the tests on all platforms and flag any
problems in JIRA as fix version 5.0M12.

Regards,
Tim

On 03/Nov/2009 21:36, Mark Hindess wrote:
> We are due another milestone build at the end of the month.  I think we
> should consider the following dates:
> 
>   Feature freeze  Fri 13th November
>   Code freeze     Fri 20st November
>   Publish         Fri 27th November
> 
> We should track issues that must be fixed for 5.0M12 with JIRA using the
> "Fix for" field.  There is currently one issues marked this way and
> I guess we should try to fix it.  To see the list visit the Harmony
> JIRA homepage at:
> 
>   http://issues.apache.org/jira/browse/HARMONY
> 
> and click on "5.0M12" entry in the Versions column.
> 
> Should we try to do "6.0M1" a week later?  (This slightly complicates the
> code freeze/thaw(?) but it spreads the work out a bit.)
> 
> Regards,
>  Mark.
> 
> 
> 

Re: [general] Milestone 12 proposed dates

Posted by Tim Ellison <t....@gmail.com>.
Reminder that we enter a feature freeze starting tomorrow -- which means
no new cool tricks to go in, bug fixing only.  Time to ramp up the
testing ready for a smooth focused test cycle starting on 20th.

Regards,
Tim

On 03/Nov/2009 21:36, Mark Hindess wrote:
> We are due another milestone build at the end of the month.  I think we
> should consider the following dates:
> 
>   Feature freeze  Fri 13th November
>   Code freeze     Fri 20st November
>   Publish         Fri 27th November
> 
> We should track issues that must be fixed for 5.0M12 with JIRA using the
> "Fix for" field.  There is currently one issues marked this way and
> I guess we should try to fix it.  To see the list visit the Harmony
> JIRA homepage at:
> 
>   http://issues.apache.org/jira/browse/HARMONY
> 
> and click on "5.0M12" entry in the Versions column.
> 
> Should we try to do "6.0M1" a week later?  (This slightly complicates the
> code freeze/thaw(?) but it spreads the work out a bit.)
> 
> Regards,
>  Mark.
> 
> 
> 

Re: [general] Milestone 12 proposed dates

Posted by Kevin Zhou <zh...@gmail.com>.
+1.

On Wed, Nov 4, 2009 at 8:05 PM, Tim Ellison <t....@gmail.com> wrote:

> Sounds good to me.
>
> Tim
>
> On 03/Nov/2009 21:36, Mark Hindess wrote:
> > We are due another milestone build at the end of the month.  I think we
> > should consider the following dates:
> >
> >   Feature freeze  Fri 13th November
> >   Code freeze     Fri 20st November
> >   Publish         Fri 27th November
> >
> > We should track issues that must be fixed for 5.0M12 with JIRA using the
> > "Fix for" field.  There is currently one issues marked this way and
> > I guess we should try to fix it.  To see the list visit the Harmony
> > JIRA homepage at:
> >
> >   http://issues.apache.org/jira/browse/HARMONY
> >
> > and click on "5.0M12" entry in the Versions column.
> >
> > Should we try to do "6.0M1" a week later?  (This slightly complicates the
> > code freeze/thaw(?) but it spreads the work out a bit.)
> >
> > Regards,
> >  Mark.
> >
> >
> >
>



-- 
Best regards,
Yours, Kevin Zhou

Re: [general] Milestone 12 proposed dates

Posted by Tim Ellison <t....@gmail.com>.
Sounds good to me.

Tim

On 03/Nov/2009 21:36, Mark Hindess wrote:
> We are due another milestone build at the end of the month.  I think we
> should consider the following dates:
> 
>   Feature freeze  Fri 13th November
>   Code freeze     Fri 20st November
>   Publish         Fri 27th November
> 
> We should track issues that must be fixed for 5.0M12 with JIRA using the
> "Fix for" field.  There is currently one issues marked this way and
> I guess we should try to fix it.  To see the list visit the Harmony
> JIRA homepage at:
> 
>   http://issues.apache.org/jira/browse/HARMONY
> 
> and click on "5.0M12" entry in the Versions column.
> 
> Should we try to do "6.0M1" a week later?  (This slightly complicates the
> code freeze/thaw(?) but it spreads the work out a bit.)
> 
> Regards,
>  Mark.
> 
> 
> 

Re: [general] Milestone 12 proposed dates

Posted by Sean Qiu <se...@gmail.com>.
+ 1 for both.

Especially 6.0M1.
It is good time to create a milestone for our 6.0 branch now, although it is
still ongoing.

Best Regards
Sean, Xiao Xia Qiu



2009/11/4 Mark Hindess <ma...@googlemail.com>

>
> We are due another milestone build at the end of the month.  I think we
> should consider the following dates:
>
>  Feature freeze  Fri 13th November
>  Code freeze     Fri 20st November
>  Publish         Fri 27th November
>
> We should track issues that must be fixed for 5.0M12 with JIRA using the
> "Fix for" field.  There is currently one issues marked this way and
> I guess we should try to fix it.  To see the list visit the Harmony
> JIRA homepage at:
>
>  http://issues.apache.org/jira/browse/HARMONY
>
> and click on "5.0M12" entry in the Versions column.
>
> Should we try to do "6.0M1" a week later?  (This slightly complicates the
> code freeze/thaw(?) but it spreads the work out a bit.)
>
> Regards,
>  Mark.
>
>
>