Everyone,
Now that we've spent a few weeks using the nsbeta1 and nsbeta1-
keywords, we've found that there is a definite need for the nsbeta1+
keyword. The driving factor is that without nsbeta1+ there is no
simple, uniform way to distinguish bugs that have been evaluated from
new nominations. (Newly nominated bugs come into the teams with various
random settings of priority and milestone, making them look just like
bugs that have already been examined and accepted for consideration.)
Each team has been using its own ad-hoc method for marking these bugs
and we want to simplify that by standardizing on nsbeta1+ instead.
Bugs with the nsbeta1+ keyword are still under consideration for
inclusion in the next release, _not_ committed. Only bugs with a
milestone have been committed. (And all nsbeta1 bugs being worked on in
the mozilla0.8 and mozilla0.9 milestones should be marked with those
milestones at this point.)
Please continue to focus on the milestone unless you are actively
participating in evaluating bugs.
Steve
