|RE: [wtp-pmc] Marking bugs for official patch|
OK. It seems that option 1 is more preferable. Therefore, I suggest that we create a new target milestone in Bugzilla, called "3.0 P", where all patch candidate bugs should be targeted. Similarly, Dali and JSF projects should have a new "2.0 P" target milestone. The "P" target milestone should be perceived as an intermediate milestone between the official release and the next maintenance release. That is "3.0 P" is after "3.0", but before "3.0.1". In this order of thoughts any bug fixed at "3.0 P" should be fixed in "3.0.1" as well.
I am not sure on how do we use the whiteboard with the "investigate" or "request patch" words. Targeting the bug to "3.0 P" implies the intention to produce an official patch for this bug. If it is later decided that this bug will not be fixed as an official patch, then it should be simply re-targeted to "3.0.1".
Nevertheless, we could use the whiteboard to determine the "solution type" of the official patch:
- "update site" to release the official patch as a "feature patch" on the update site.
- "rebuild plugin" to rebuild the patched plugin, so the adopter can simply include it in his product.
Does the above seem reasonable?
Regarding the "milestone cleanup". I doubt it is reasonable hiding certain milestones, if possible at all. While we want need most of them on the bug's page, we should have all of them displayed in the search page. However we could improve the situation by rearranging the sortkey of the milestones. So, the recent ones are on the top. I imagine something like this:
The "---" milestone has the sortkey = "0". I think this makes it the default milestone. I have to check if negative sortkeys are possible, to milestones with negative sortkeys can pop above the "---" one.
An important note is that sortkeys of already created milestones cannot be changed by the Portal (I will file a bug about this), but only through are request to the webmaster.
From: wtp-pmc-bounces@xxxxxxxxxxx [mailto:wtp-pmc-bounces@xxxxxxxxxxx] On Behalf Of raghunathan.srinivasan@xxxxxxxxxx
Sent: Thursday, June 19, 2008 1:11 AM
To: WTP PMC communications (including coordination, announcements, and Groupdiscussions)
Subject: RE: [wtp-pmc] Marking bugs for official patch
I vote for option1, a new target milestone for each patch ‘release’ for the corresponding official release.
From: David M