mozilla 1.0.1 update...
Judson Valeski
down approvals by minusing requests that don't meet the further
restricted criteria. A few weeks ago the following criteria was posted
for 1.0.1 checkins.
"To provide more clarification regarding what we're targeting 1.0.1
for... we are generally looking for fixes to _high_ visibility problems,
stability improvements (topcrash bugs), & near zero risk polish issues.
The scope of 1.0.1 is more narrow than 1.0. Not everything that was
declined for 1.0 should be requesting 1.0.1 checkins. Yes, the 1.0
branch is going to be alive for awhile, but, architecture work, feature
work, risky changes, edge case work, and the like should be happening in
our life blood, the trunk; not the 1.0.1 branch."
Now we're looking for even _higher_ visibility problems. topcrash is
topcrash is topcrash. Low risk fixes to topcrash bugs are always strong
candidates. We're shooting for nearly full lock down by Monday (the 24th
of June), so, if you have bugs you want to include in 1.0.1 (that meet
the above, further, narrowed criteria), send them to
dri...@mozilla.org. We are only fielding bugs that have landed on the
trunk and have baked there for at least two days, and that have been
verified as resolved on the trunk.
Will there be a 1.0.2? If there's a need, there will be a 1.0.2.
Jud