Re: Confusing tracker bug naming
On 10/06/2012 08:42 PM, Christoph Wickert wrote: Questions, feedback, thoughts or rants anybody? This is something you should be asking on the -test list where the QA community resides JBG -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Confusing tracker bug naming
Currently Blocker bugs are named Freleasemilestone: * FXXAlpha * FXXBeta * FXXBlocker To indicate whether something was accepted as a blocker or not the whiteboard is used: AcceptedBlocker or RejectedBlocker Nice-to-have bugs are named Freleasemilestone-accepted: * FXXAlpha-accepted * FXXBeta-accepted * FXX-accepted To indicate whether something was accepted as a nice-to-have or not again the whiteboard is used: AcceptedNTH or RejectedNTH. This is inconsistent and confusing: 1. Blocker bugs for alpha and beta don't have blocker in their name but the final has. 2. Naming the NTH bugs -accepted can be easily confused with the whiteboard status and sounds like an accepted blocker, but not like only nice-to-have. Therefor I propose: * FreleaseMilestoneBlocker, that is FXXAlphaBlocker, FXXBetaBlocker, FXXBlocker. * FreleaseMilestoneNTH, that is FXXAlphaNTH, FXXBetaNTH, FXXNTH * Whiteboard remains unchanged. Questions, feedback, thoughts or rants anybody? Kind regards, Christoph -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Confusing tracker bug naming
Here was my proposal: https://fedoraproject.org/wiki/Talk:BugZappers/HouseKeeping/Trackers -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Confusing tracker bug naming
Am Samstag, den 06.10.2012, 23:47 + schrieb Andre Robatino: Here was my proposal: https://fedoraproject.org/wiki/Talk:BugZappers/HouseKeeping/Trackers For the list: Robin's proposal is * 15Alpha, 15Beta and 15Final (or alternatively 15) * 15AlphaNTH, 15BetaNTH and 15FinalNTH (or alternatively 15NTH) So we agree that having two different labels for one thing (NTH and accepted) is confusing and that 'accepted' is even worse because it can be confused with the whiteboard statuses. I think just a number (like 15) is not enough. The advantage I see for my proposal is that the it is consistent not only throughout the names of the tracker bugs but throughout both bug names and whiteboard statuses: Blocker in the whiteboard can only exist in a Blocker bug. But this is only a minor difference that I don't really care about as long as we get change the current 'accepted' names. :) Best regards, Christoph -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Confusing tracker bug naming
On Sun, 2012-10-07 at 02:23 +0200, Christoph Wickert wrote: Am Samstag, den 06.10.2012, 23:47 + schrieb Andre Robatino: Here was my proposal: https://fedoraproject.org/wiki/Talk:BugZappers/HouseKeeping/Trackers For the list: Robin's proposal is * 15Alpha, 15Beta and 15Final (or alternatively 15) * 15AlphaNTH, 15BetaNTH and 15FinalNTH (or alternatively 15NTH) So we agree that having two different labels for one thing (NTH and accepted) is confusing and that 'accepted' is even worse because it can be confused with the whiteboard statuses. I think just a number (like 15) is not enough. The advantage I see for my proposal is that the it is consistent not only throughout the names of the tracker bugs but throughout both bug names and whiteboard statuses: Blocker in the whiteboard can only exist in a Blocker bug. But this is only a minor difference that I don't really care about as long as we get change the current 'accepted' names. :) Yeah, we have several proposals. The good thing is that BZ aliases aren't exclusive, a bug can have as many as you like. Heck, we could add all the proposals as aliases to the F18 bugs, even. Whatever floats your boat. =) I don't mind doing that, but a (slightly) less radical plan would be to add all the proposals as aliases to the F19 bugs and see how people like 'em. That wouldn't be too difficult, it'd only take someone maybe an hour to go and unearth all the proposals and edit the bugs. Anyone want a ticket to do it? -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
