On Thu, Dec 23, 2010 at 11:25, Carsten Munk <[email protected]> wrote: > > I meant a metabug along lines of http://bugs.meego.com > /showdependencytree.cgi?id=11429&hide_resolved=0 for the GPLv3 stuff, not > for the reason that we have a requirement of having bugs for getting accepted. > > Reason for this would be to help to track issues happening because of the > downgrades and allow people to see what'll change in order to prepare for > the downgrades.
Certainly if there's been an edict/recognition that some GPLv3 packages have come in there should be a single bug against which all the downgrades & changes are happening, IMHO. Having a reminder go out "you can't use a GPLv3 package" (or whatever it was) and then have *each maintainer* raise their own issue is a bit... odd. Having a single meta-bug, which may have child bugs _if the individual maintainers want it_ allows better tracking of progress and a cohesive change to the project to be tracked. Again, IMHO/IME/YMMV etc. etc. Cheers, Andrew -- Andrew Flegg -- mailto:[email protected] | http://www.bleb.org/ Maemo Community Council member _______________________________________________ MeeGo-packaging mailing list [email protected] http://lists.meego.com/listinfo/meego-packaging
