Moving to bugzilla

[Till Schneidereit]

Hey All,

we recently decided to move to bugzilla.mozilla.org for bug tracking.

What does that entail?
- we'll track feature development and bug fixes in bugzilla bugs instead of
github issues
- we'll mention bugs in commits/ pull requests
- we'll link to github pull requests in bugzilla bugs when closing them

What *doesn't* that entail?
- we won't move off of github for source management
- we won't move to bugzilla's Splinter tool for code reviews (*shudder*)
- we won't mass-move all issues to bugzilla, at least for now
- we won't remove the ability to file new github issues, and we're not
likely to do so in the future: more people have github accounts than
bugzilla.mozilla.org accounts, so we'd make it harder to report issues. We
might move actionable things over to bugzilla on a case-by-case basis

What does that mean for you?
- to follow everything that's going on in Shumway, watching the project on
github isn't enough, anymore
- if you want to still do that, you can use the "component watching"
feature in bugzilla[1] and watch the Shumway component in the Firefox
product

Why are we doing this?
- github issues are ... basic
- they don't support dependencies so we can't effectively manage meta bugs
- the notification system is severely lacking, so it's hard to keep track
of things
- bugzilla.mozilla.org is used by most Mozilla projects. Crucially, we
somewhat frequently have dependencies on Firefox platform bugs and want to
be able to express and track those
- we'll probably have security-sensitive bugs in the future, and bugzilla
allows us to hide those
- surprisingly (to me, a while ago, at least) bugzilla is a very nice and
extremely powerful tool


that is all.


[1]: https://bugzilla.mozilla.org/userprefs.cgi?tab=component_watch