SeaMonkey will be boarding the release train, and has a new release coming out, this bug will be for all the updates we need/want done for Bugzilla, can be done in mini-batches, but I plan to outline the whole list here in c#0. SeaMonkey Product unless otherwise specified. For the |Version| field we should insert between "SeaMonkey 2.0 Branch" and "Trunk" the following values: * SeaMonkey 2.1 Branch * SeaMonkey 2.2 Branch * SeaMonkey 2.3 Branch For |target-milestone|: * move the '---' sep to after 2.1final * rename "seamonkey2.2a1" to "seamonkey2.2" * add "seamonkey2.3" Basic-Bug-Flags: * blocking-seamonkey-2.0.14 -- retire, no longer settable if not present (and hidden on new bugs) Complex/Custom-Flags: * blocking-seamonkey-2.1 -- ** disable needed, a1+, a2+, a3+, b1+, b2+, b3+ ** add MU+ * status-seamonkey-2.1 -- ** add .1-fixed New Custom Fields (to have same perms as the custom blocking/status fields above, namely seamonkey-council can set every value, anyone can request -- visible in "SeaMonkey" and "Mailnews Core" products) * tracking-seamonkey-2.2 ** ? ** + ** - * tracking-seamonkey-2.3 ** ? ** + ** - Attachment Flags: * approval-seamonkey2.0.14 -- retire, no longer settable if not present (and hidden on new bugs) * approval-seamonkey2.1b2 -- retire, no longer settable if not present (and hidden on new bugs) * approval-seamonkey2.1b3 -- retire, no longer settable if not present (and hidden on new bugs) * approval-comm-aurora -- new, duplicate settings from existing approval-seamonkey2.1 [note, these "who can set" settings may change, for sharing with Thunderbird Drivers]

all changes made except for the two new custom fields (tracking-seamonkey-2.2 and tracking-seamonkey-2.3)

new custom field code support committed: Committing to: bzr+ssh://bjones%40mozilla.com@bzr.mozilla.org/bmo/4.0/ modified extensions/BMO/lib/Data.pm Committed revision 7695. justdave: please update staging-tip to current and add the two new custom fields to staging-tip: > tracking-seamonkey-2.2 > tracking-seamonkey-2.3

You can probably get away with creating these on the web ui on staging. The liklihood of colliding with someone updating a bug is a lot lower.

(In reply to comment #3) > You can probably get away with creating these on the web ui on staging. The > liklihood of colliding with someone updating a bug is a lot lower. i'd love to, but the web ui for cf creation is disabled (bug 646476).

(In reply to comment #2) > new custom field code support committed: > > Committing to: bzr+ssh://bjones%40mozilla.com@bzr.mozilla.org/bmo/4.0/ > modified extensions/BMO/lib/Data.pm > Committed revision 7695. > > justdave: please update staging-tip to current and add the two new custom > fields to staging-tip: > > > tracking-seamonkey-2.2 > > tracking-seamonkey-2.3 Ping on these, and now we want/need -2.4 as well.

these have been created on https://bugzilla-stage-tip.mozilla.org now if you could please verify they look correct. If yes, then I will add these to production later today when traffic is lower. dkl

(In reply to comment #6) > these have been created on https://bugzilla-stage-tip.mozilla.org now if you > could please verify they look correct. The correct fields seem to exist there, the values to set them to not, is that expected?

(In reply to comment #7) > (In reply to comment #6) > > these have been created on https://bugzilla-stage-tip.mozilla.org now if you > > could please verify they look correct. > > The correct fields seem to exist there, the values to set them to not, is > that expected? Sorry bout that. The staging server is using a sanitized db which meant all groups were removed. I added the necessary groups that will make the new custom fields act similarly to production. Please try to verify once more. dkl

(In reply to comment #8) > (In reply to comment #7) > > (In reply to comment #6) > > > these have been created on https://bugzilla-stage-tip.mozilla.org now if you > > > could please verify they look correct. > > > > The correct fields seem to exist there, the values to set them to not, is > > that expected? > > Sorry bout that. The staging server is using a sanitized db which meant all > groups were removed. I added the necessary groups that will make the new > custom fields act similarly to production. Please try to verify once more. Now that I can login on the stage-tip server, I see (logged in, with seamonkey-council perms) only teh ability to request the flag '?' not the ability to set any actual values.

(In reply to comment #9) > Now that I can login on the stage-tip server, I see (logged in, with > seamonkey-council perms) only teh ability to request the flag '?' not the > ability to set any actual values. Sigh. Created the groups but forgot to add you to them :( Please try one more time. dkl

(In reply to comment #10) > (In reply to comment #9) > > Now that I can login on the stage-tip server, I see (logged in, with > > seamonkey-council perms) only teh ability to request the flag '?' not the > > ability to set any actual values. > > Sigh. Created the groups but forgot to add you to them :( Please try one > more time. Ok, looks good now; thank you.

New fields created on production site. I believe all of the other tasks were completed before. dkl