Bugzilla recommendation
Mark Hatle
mark.hatle at windriver.com
Fri Mar 18 20:55:38 UTC 2011
On 3/18/11 2:41 PM, Koen Kooi wrote:
> Hi,
>
> On oe-devel is was suggested that the TSC make a recommendation of the
> bugzilla situation. I would like to propose the following:
>
> Shutdown the current OE bugzilla and add a html page directing people to
> patchwork and the mailinglist. We can alway reactivate bugzilla when someone
> actually steps up instead of the current "I might..." type of people.
Shutdown, as in make read-only or? I'd hate to lose anything that may be
valuable in it.
> For OE-core we will (re)use the yocto bugzilla, other layers should document
> their bug policy clearly inside the layer README.
>
> I think this accomplishes what RP and I want, no zombie bugzillas and keeps
> the door open for people willing to maintain one. What do you all think of
> this?
I think we need to be clear when we suggest shutting it down that if someone is
willing to manage a subsystem and take responsibility for work that there be a
way to enable a bug tracking system. But it's only for components, projects
that have an active maintainer, someone responsible for dealing with the bugs.
--Mark
> regards,
>
> Koen
>
> PS: It looks like angstrom will go with Jira for its layer(s) and distro.
> _______________________________________________ tsc mailing list
> tsc at lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/tsc
More information about the tsc
mailing list