After review from the people affected of the proposed changes in the way we are tracking nominations for the next commercial Netscape release, we decided that until the bug tracking system handles bug aliases (i.e., allows you to name tracking bug # 1111111 as nextNetscapeCommercialReleaseNominations [or nsbeta1 to keep it familiar :-)]) and until we provide "cookbooks" for the new process, we will keep the current process.
I have copied the appropriate keyword semantics below.
| nsbeta1 | Use this keyword to nominate a bug to be fixed for the next Netscape release. Bugs which have been rejected for consideration in the next Netscape release will have the nsbeta1 keyword replaced with the nsbeta1- keyword. To renominate a bug which has been rejected replace the nsbeta1- with the nsbeta1 keyword. |
|---|---|
| nsbeta1+ | Bugs which are still under consideration for the next Netscape release will have the nsbeta1 keyword replaced with the nsbeta1+ keyword. |
| nsbeta1- | Bugs which have been rejected for consideration in the next Netscape release will have the nsbeta1 keyword replaced with the nsbeta1- keyword. To renominate a bug which has been rejected replace the nsbeta1- with the nsbeta1 keyword. |
|---|
Note that we have 1512 existing bugs with nsbeta1, nsbeta1+ and nsbeta1- keywords (500+ are nsbeta1).
We will start with the clean slate for those, but to preserve easily accessible history ....
... sometime today Asa Dotzler will create three tracking bugs (one for the current nsbeta1 bugs, one for the current nsbeta1+ bugs and one for the current nsbeta1- bugs). He will add all the current nsbeta1, nsbeta1+ and nsbeta1- bugs to the appropriate tracking bug. After that he will clear all current nsbeta1, nsbeta1+ and nsbeta1- keywords.
If you nominated or triaged the bugs recently using nsbeta1* then you may lose your nomination, "plussness" or rejection.
Here are the ways to find your bug(s) and redo them [after the above process is done]:
- go to the bugzilla query page
- enter the data for query for your team, component, bugs that you reported, bugs that you own, etc ...
- IN ADDITION (find the two drop down fields and a text entry field below keywords query field)
** select OtherBugsDependingOnThis in the first drop down list
** select equal to in the second drop down list
** enter xxxxx where xxxxx will be the tracking bug number for the removed nsbeta1 or nsbeta1+ or nsbeta1- bugs (to be communicated by Asa)
(note that is the way you can treat tracking bug [numbers at this point; named aliases in the future] and keywords as equivalent)
** press submit query
Note that a similar operation will be also performed for bugscape bugs.
Marek
PS. we will return to getting education, listening to the feedback, etc.. using tracking bugs in our process the near future.
http://bugzilla.mozilla.org/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&email1=&emailtype1=substring&emailassigned_to1=1&email2=&emailtype2=substring&emailreporter2=1&bugidtype=include&bug_id=&changedin=&votes=&chfieldfrom=&chfieldto=Now& chfieldvalue=&short_desc=&short_desc_type=allwordssubstr&long_desc=&long_desc_type=allwordssubstr&bug_file_loc=&bug_file_loc_type=allwordssubstr&status_whiteboard=&status_whiteboard_type=allwordssubstr&keywords=nsbeta1+nsbeta1%2B+nsbeta1-&keywords_type=anywords&field0-0-0=noop&type0-0-0=noop&value0-0-0=&cmdtype=doit&newqueryname=&order=Reuse+same+sort+as+last+time
