<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"></head><body>
<div>I agree and I'm willing to help get things going.</div><div><br></div><div><br></div><div><br></div><div id="composer_signature"><meta http-equiv="Content-Type" content="text/html; charset=UTF-8">--<div>Denis Roy </div><div>@droy_eclipse</div><div>http://eclipse.org/</div></div><br><br>-------- Original message --------<br>From: Frédéric Buclin <lpsolit@gmail.com> <br>Date: 2015-11-29 9:33 AM (GMT-05:00) <br>To: developers@bugzilla.org <br>Subject: Have a separate Bugzilla installation for the Bugzilla project? <br><br>Hi all,<br><br>Seeing how things are going in the Mozilla world, I would suggest that<br>the Bugzilla project has its own Bugzilla installation, managed by the<br>upstream Bugzilla team itself. More and more users do not understand<br>that BMO != upstream Bugzilla, and having their own installation running<br>unmodified current tip code (currently 5.1) would help 1) users to<br>discover newly implemented features, and 2) developers to find regressions.<br><br>BMO UI and backend code differ more and more from upstream Bugzilla;<br>some features which exist upstream are being removed from BMO, such as<br>personal tags, see bug 1227316; many bugs reported by Mozilla users are<br>specific to BMO and do not affect upstream. So IMO it makes sense to<br>close the Bugzilla product in BMO and manage upstream bugs in their own<br>Bugzilla installation instead.<br><br>What do you think? Ignore import/export of existing bugs for now. This<br>is not the most critical part.<br><br>Myk filed a bug about this migration a long time ago, see<br>https://bugzilla.mozilla.org/show_bug.cgi?id=127876.<br><br><br>LpSolit<br><br>-<br>To view or change your list settings, click here:<br><http://bugzilla.org/cgi-bin/mj_wwwusr?user=denis.roy@eclipse.org><br></body></html>