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/08/15 00:23:02 UTC
[general] Milestone 11 preparation: entering feature freeze
We are entering feature freeze now and there is one week until the code
freeze. No major new functionality should be committed from now until
M11 is released. Commits specifically for bug fixes are permitted.
We should track issues that must be fixed for M11 with JIRA using the
"Fix for" field. To see the current must fix issues visit the Harmony
JIRA homepage at:
http://issues.apache.org/jira/browse/HARMONY
and click on "5.0M11" entry in the Versions column.
There are currently a few issues marked this way but I don't think all
of them are actually "must fix" issues. If any of these issues were
reported by you and/or assigned to you please review them and confirm
that the "must fix" status is warranted or remove it (or fix it if it is
a bug I suppose).
Regards,
Mark.
Re: [general] Milestone 11 preparation: entering feature freeze
Posted by Sean Qiu <se...@gmail.com>.
I saw you help remove some Java 6 branch jiras from "must fix in
5.0M11", thanks, Mark.
Everyone, to facilitate our milestone release, we need pay more
attention to these jira fields.
We'd better let it remain its default value for all Java 6 issues.
Best Regards
Sean, Xiao Xia Qiu
2009/8/15 Mark Hindess <ma...@googlemail.com>:
>
> We are entering feature freeze now and there is one week until the code
> freeze. No major new functionality should be committed from now until
> M11 is released. Commits specifically for bug fixes are permitted.
>
> We should track issues that must be fixed for M11 with JIRA using the
> "Fix for" field. To see the current must fix issues visit the Harmony
> JIRA homepage at:
>
> http://issues.apache.org/jira/browse/HARMONY
>
> and click on "5.0M11" entry in the Versions column.
>
> There are currently a few issues marked this way but I don't think all
> of them are actually "must fix" issues. If any of these issues were
> reported by you and/or assigned to you please review them and confirm
> that the "must fix" status is warranted or remove it (or fix it if it is
> a bug I suppose).
>
> Regards,
> Mark.
>
>
>