Bugs required to be fixed for SeaMonkey 1.0 final release

RESOLVED FIXED

Status

SeaMonkey
General
RESOLVED FIXED
11 years ago
11 years ago

People

(Reporter: Ian Neal, Unassigned)

Tracking

({fixed1.8.0.1})

Trunk
fixed1.8.0.1
Dependency tree / graph
Bug Flags:
blocking-seamonkey1.0 +

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: tracking)

(Reporter)

Description

11 years ago
This is a tracking bug for those bugs that need to checked in prior to SeaMonkey 1.0 final release. Most, but not all, will have a blocking-seamonkey1.0+ flag already.
Bug numbers should be put in the "Depends on" field but also a short summary put in the comment field.
(Reporter)

Updated

11 years ago
Flags: blocking-seamonkey1.0+
Whiteboard: tracking
315325 - remove remote content UI - this patch should land *only* on 1.8.0
Depends on: 315325
(Reporter)

Comment 2

11 years ago
Bug 322381 is best to go in now bug 321601 has gone in, though patch author should make sure mozilla-l10n are warned.
Depends on: 322381
(Reporter)

Comment 3

11 years ago
Bug 319659 needs to be in too, see Bug 319659#5 for details
Depends on: 319659

Comment 4

11 years ago
If it was up to me, bug 291386 would surely be set to blocking-seamonkey1.0+. It annoys me daily on OS/2, and my nephew won't even use CZ on XP any more because of it.
This isn't for nominations of bugs - it's so we can make sure we land all patches that exist, have review, and council approval, because we're not allowed to check in to 1.8.0 right now.  We want to be ready to land everything as soon as we are allowed to on 1.8.0 and ship ASAP after that.

Comment 6

11 years ago
IanN, I'll announce both bug 322381 and bug 321526 in mozilla-l10n
Depends on: 321526

Comment 7

11 years ago
Bug 323539 - "JS warning opening MailNews / selecting folders" (Patch for branches)
Depends on: 323539

Comment 8

11 years ago
I would recomend bug #184042, cause some bank sites requires java to be enabled

Comment 9

11 years ago
Why do we have this bug?
We created blocking flags to exactly not need that kind of silly bug reports...
(In reply to comment #9)
> Why do we have this bug?
> We created blocking flags to exactly not need that kind of silly bug reports...

This is specifically for tracking landings on 1.8.0 since the tree is closed and we can't check patches in now.

Comment 11

11 years ago
I still se no reason at all for this bug to be around (other than wasting resources) - but then I'm not the release manager.
(Reporter)

Updated

11 years ago
Depends on: 323970
dveditz unclosed 1.8.0.

Patches to SeaMonkey-only code can land if council has given approval.
Patches to shared code need approval from drivers *after* council has given approval.
Depends on: 321128

Comment 13

11 years ago
Hi,
Since we havde all of the bugs in here resolved as fixed we should do the same with this bug.
Sorry for bug spam but I am doing a request.

Comment 14

11 years ago
(In reply to comment #13)
> Hi,
> Since we havde all of the bugs in here resolved as fixed we should do the same
> with this bug.
> Sorry for bug spam but I am doing a request.
> 

No, not all bugs that are marked fixed are fixed on 1.8.0 branch.

Comment 15

11 years ago
Hi,
All of Bug 323357 depends on:	315325 319659 321128 321526 322381 323539 323970 are lined out.
Are you sure that this is still needed?
(In reply to comment #15)
> Hi,
> All of Bug 323357 depends on:   315325 319659 321128 321526 322381 323539
> 323970 are lined out.
> Are you sure that this is still needed?
> 

We will close this bug when we're done with it.

Updated

11 years ago
Depends on: 322459

Comment 17

11 years ago
Err, bug 322459 - a few changes in the help doc. Needs to be announced in l10n newsgroup (Giacomo?)

Comment 18

11 years ago
I won't be able to do that until Tuesday at the earliest (out of town). If someone can do that first, please do so.
Since the tree is no longer closed, this bug can be resolved.
Status: NEW → RESOLVED
Last Resolved: 11 years ago
Resolution: --- → FIXED

Comment 20

11 years ago
getting this off the oustanding blockers list
Keywords: fixed1.8.0.1
You need to log in before you can comment on or make changes to this bug.