Should 3.0a3 be pushed back

[JoeS]

I think so. The downgrade from b1 to a3 is not enough to justify a release in the current state of the trunk.

Here's my short list:
https://bugzilla.mozilla.org/show_bug.cgi?id=431819
https://bugzilla.mozilla.org/show_bug.cgi?id=429118
https://bugzilla.mozilla.org/show_bug.cgi?id=457975
https://bugzilla.mozilla.org/show_bug.cgi?id=451599
https://bugzilla.mozilla.org/show_bug.cgi?id=453943
IMHO an over-reaction to:
https://bugzilla.mozilla.org/show_bug.cgi?id=451599

--
JoeS

[Mark Banner]

On 2/10/08 02:18, JoeS wrote:
> I think so. The downgrade from b1 to a3 is not enough to justify a
> release in the current state of the trunk.

Thank you for your comments, its good to know other people are keeping
an eye on the bugs as well as the drivers.

What you have to remember is that this is now an alpha release. This
means that it likely isn't going to be perfect, and we expect some
issues. We're releasing to get feedback on the new ideas going into the
build and we may have got some bits wrong.

With that in mind:

> Here's my short list:
> https://bugzilla.mozilla.org/show_bug.cgi?id=431819

This got backed out at an unfortunate time. We have decided that we'll
add it back to mozilla-central just for the release. We'll then look at
getting this properly addressed in the next cycle.

> https://bugzilla.mozilla.org/show_bug.cgi?id=429118

This is a problem in spell check, generally spell check does work,
though there is some situations (like in this bug) where it can break.
We'd would have liked this to be fixed, but the fix needs more work, and
hence we've decided that unless it gets in by the time we cut the tree,
then we will try and fix it for the next release.

> https://bugzilla.mozilla.org/show_bug.cgi?id=457975

This is a minor bug that something doesn't quite work with the new
buttons. As we are already well past code-freeze now, we tend to
restrict unnecessary changes to things that really block, otherwise we'd
just go on in code-freeze forever.

> https://bugzilla.mozilla.org/show_bug.cgi?id=451599

Again this is similar to the last one. The feature is new, the UI for
clearing the cache isn't there. We don't see that as a major issue,
we'll be mentioning it in the release notes though.

> https://bugzilla.mozilla.org/show_bug.cgi?id=453943
> IMHO an over-reaction to:

> https://bugzilla.mozilla.org/show_bug.cgi?id=453928

I've corrected the second bug number. The issue here is one of security.
Due to the late change in core, we felt that a) we did not have time for
a proper fix before the release, and b) we do not want to risk the
security of testers.

Additionally, we're looking for feedback as to how many folks this will
actually affect. We suspect that releasing an alpha may get some
additional feedback.

Hopefully that explains our thinking. We're currently looking at cutting
the release today or tomorrow and being able to move on from there.

Regards
Standard8