Closed Bug 1461060 Opened 2 years ago Closed 2 years ago

Please add Target "SeaMonkey2.59", {status,tracking}-seamonkey2.59, and approval-comm-esr60 (SM variant)

Categories

(bugzilla.mozilla.org :: Administration, task)

Production
task
Not set

Tracking

()

VERIFIED FIXED

People

(Reporter: rsx11m.pub, Unassigned)

References

Details

+++ This bug was initially created as a clone of Bug #1459838 +++

Please add approval-comm-esr60 as flag for attachments in the SeaMonkey product, which should be distinct from approval-comm-esr60 for Thunderbird (see approval-comm-esr52 setup).

Please also add SeaMonkey2.59 as Target Milestone. Thanks!
The status-seamonkey2.59 and tracking-seamonkey2.59 flags are missing as well.
Summary: Please add Target "SeaMonkey2.59", and approval-comm-esr60 (SM variant) → Please add Target "SeaMonkey2.59", {status,tracking}-seamonkey2.59, and approval-comm-esr60 (SM variant)
Done. You have several older versions of SeaMonkey in your flags, can those be disabled, and how many versions back do you want active and select-able?
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
Thanks.

2.49esr is the current release from the ESR 52 release branch. We are keeping 2.53 for now because we might need an interim release with backported security fixes till 2.57esr (releese/esr60) is ready. 2.58 and 2.59 are beta and central.

So release flags are fine for now.

But we still seem to have an approval‑comm‑aurora in the details for Attachments/patches. This should go. Should I file a new bug?
Flags: needinfo?(ehumphries)
Thanks - I see "2.8" and "2.9" now added as Target Milestone (without "SeaMonkey") following the current trunk version, which I don't recall having seen there before. There are still separate "SeaMonkey2.8" and "SeaMonkey2.9" milestones, those are ok.
Flags: needinfo?(ehumphries)
I think that may have been an error in the script that was used to add new milestones. I've moved the two bugs affected to 2.58 and 2.59 respectively and removed those milestones.
Flags: needinfo?(ehumphries)
Thanks, looks good now.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.