Have a separate Bugzilla installation for the Bugzilla project?

[Denis Roy]

As I've posted on the bug, I'm behind this and Eclipse can offer a pair
of load-balanced virtual servers to which the core developers all have
root accces to, to run Bugzilla, the build system and whatever is
needed. Eclipse IT staff will also maintain (sysadmin) the servers so
that core devs don't have to waste their time on this task.

Denis



On 11/29/2015 09:33 AM, Frédéric Buclin wrote:
> Hi all,
> 
> Seeing how things are going in the Mozilla world, I would suggest that
> the Bugzilla project has its own Bugzilla installation, managed by the
> upstream Bugzilla team itself. More and more users do not understand
> that BMO != upstream Bugzilla, and having their own installation running
> unmodified current tip code (currently 5.1) would help 1) users to
> discover newly implemented features, and 2) developers to find regressions.
> 
> BMO UI and backend code differ more and more from upstream Bugzilla;
> some features which exist upstream are being removed from BMO, such as
> personal tags, see bug 1227316; many bugs reported by Mozilla users are
> specific to BMO and do not affect upstream. So IMO it makes sense to
> close the Bugzilla product in BMO and manage upstream bugs in their own
> Bugzilla installation instead.
> 
> What do you think? Ignore import/export of existing bugs for now. This
> is not the most critical part.
> 
> Myk filed a bug about this migration a long time ago, see
> https://bugzilla.mozilla.org/show_bug.cgi?id=127876.
> 
> 
> LpSolit
> 
> -
> To view or change your list settings, click here:
> <http://bugzilla.org/cgi-bin/mj_wwwusr?user=denis.roy@eclipse.org>
>