hi! well, when I propose this, it was for tracking the progress, I abuse the blocker name :)
I mean, I didn't want to make all the roadmap whislist a blocker for 2.22, just put all in the bugzilla and have a better way to keep track of the progress, et al cheers, El dj 29 de 11 del 2007 a les 11:09 +0100, en/na Andre Klapper va escriure: > ahoj, > > Bruno Boaventura píše v St 28. 11. 2007 v 17:13 -0300: > > On Nov 28, 2007 2:03 PM, Gil Forcada <[EMAIL PROTECTED]> wrote: > > > > I was wondering if it will be useful to have a blocker named GNOME 2.22 > > > > in bugzilla and the same for every app in GNOME and enter (or marked as > > > > a dependency) of the first one, finally every feature planned in the > > > > RoadMap should be filled and marked as a dependency for the per-app > > > > blocker > > > > > > > > for what? just to keep track, since bugzilla marks the resolved bugs, a > > > > brief look at the global blocker will tell us if the GNOME 2.22 global > > > > RoadMap (or per-app) is going well :) > > > > I think the roadmaps are not mandatory, they may not be met by some > > modules, thus we can't block the release because of roadmaps. > > > > What are other bugsquaders' opinions? > > i think you mentioned to different things here. :) > > we have gnome-target milestones in bugzilla, see > http://bugzilla.gnome.org/buglist.cgi?query=meta-status:open,needinfo+gnome-target=2.22.x > this is a setting for blockers only, means worst crashers or big > interoperability or compile problems. it's not a "we would like to have > this done by 2.22" wishlist. > > if we would have a GNOME 2.22 tracking/metabug and add other roadmap > stuff as dependencies, it would indeed be easier to track progress and > control of how much of aims were achieved. in this case it also wouldn't > matter whether roadmap tasks are mandatory or not. evolution had a > tracking bug for gnome 2.13 (see > http://bugzilla.gnome.org/show_bug.cgi?id=327508 ) and there are still a > lot of unresolved dependencies, because it was abused as a wishlist bug. > another way could be to add a status whiteboard entry like > "roadmap[2.22]" to the affected bug reports. basically the same as > above, advantage: don't count the numbers manually (because bugzilla's > query will tell you), disadvantage: you can't CC to the metabug and get > informed of fixed dependencies. > > andre -- gil forcada [ca] guifi.net - una xarxa lliure que no para de créixer [en] guifi.net - a non-stopping free network bloc: http://gil.badall.net _______________________________________________ Gnome-bugsquad mailing list [email protected] http://mail.gnome.org/mailman/listinfo/gnome-bugsquad
