[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[wtp-pmc] Marking bugs for official patch
- From: "Raev, Kaloyan" <kaloyan.raev@xxxxxxx>
- Date: Wed, 18 Jun 2008 14:19:33 +0200
- Delivered-to: email@example.com
- Thread-index: AcjRPZE38G50NokxQ6SkH8N2NsO/kQ==
- Thread-topic: Marking bugs for official patch
We talked on the PMC call yesterday that we need a way to clearly mark
bugs that require to be released as an official patch.
I see three possible several possible ways to do this in Bugzilla.
1. Target Milestone. A dedicated Target Milestone for each official
release that we provided official patches needs to be added. Example:
"3.0 P" or "3.0 PATCHES". We expect only few patches for a release.
Therefore creating a special Target Milestone does not seem reasonable.
2. Keyword. A dedicated keyword can be to the bug. Example: "patch" or
"officialpatch". Adding keywords is a global bugzilla setting and should
be made by the webmaster.
3. Whiteboard. A dedicated word can be added to the Whiteboard field.
Similar to the Keyword approach. We use the Whiteboard to mark bugs for
PMC approval. Typically, all "official patch" bugs should be approved by
the PMC. Therefore, we will always have overlapping in this field.
4. Summary. A "[patch]" prefix can be added to the Summary of the bug.
We use this approach also for "hotbugs". Most of the "official patch"
bugs are also hotbugs. Overlapping could happen here as well.
For me the most reasonable approach is to mark the bugs with the keyword
"officialpatch" (option 2). If all of you are comfortable with this I
can request the webmaster to add this keyword to Bugzilla.
Eclipse WTP Committer
NW C JS TOOLS JEE (BG)
SAP Labs Bulgaria
P Save a tree - please do not print this email unless you really need