Have a separate Bugzilla installation for the Bugzilla project?

classic Classic list List threaded Threaded
15 messages Options
Reply | Threaded
Open this post in threaded view
|

Have a separate Bugzilla installation for the Bugzilla project?

Frédéric Buclin
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=lists+s6506n84121h51@...>
Reply | Threaded
Open this post in threaded view
|

Re: Have a separate Bugzilla installation for the Bugzilla project?

Jochen Wiedmann
Makes quite some sense to me.

Jochen

On Sun, Nov 29, 2015 at 3:33 PM, Frédéric Buclin <[hidden email]> 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=jochen.wiedmann@...>



--
The next time you hear: "Don't reinvent the wheel!"

http://www.keystonedevelopment.co.uk/wp-content/uploads/2014/10/evolution-of-the-wheel-300x85.jpg
-
To view or change your list settings, click here:
<http://bugzilla.org/cgi-bin/mj_wwwusr?user=lists+s6506n84121h51@...>
Reply | Threaded
Open this post in threaded view
|

Re: Have a separate Bugzilla installation for the Bugzilla project?

Denis Roy
In reply to this post by Frédéric Buclin
I agree and I'm willing to help get things going.



--
Denis Roy 
@droy_eclipse
http://eclipse.org/


-------- Original message --------
From: Frédéric Buclin <[hidden email]>
Date: 2015-11-29 9:33 AM (GMT-05:00)
To: [hidden email]
Subject: Have a separate Bugzilla installation for the Bugzilla project?

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=[hidden email]>
Reply | Threaded
Open this post in threaded view
|

Re: Have a separate Bugzilla installation for the Bugzilla project?

Frédéric Buclin
In reply to this post by Jochen Wiedmann
I forgot to mention:

The Testopia product on BMO should also be moved to the new Bugzilla
installation as it's tied to upstream Bugzilla, not BMO.

As I see it, this could make things easier to manage and develop
Bugzilla extensions, as each extension could have its own product on the
new installation, with its own set of contributors. Something similar to
what Mozdev did:

https://www.mozdev.org/bugs/describecomponents.cgi


LpSolit

-
To view or change your list settings, click here:
<http://bugzilla.org/cgi-bin/mj_wwwusr?user=lists+s6506n84121h51@...>
mva
Reply | Threaded
Open this post in threaded view
|

Re: Have a separate Bugzilla installation for the Bugzilla project?

mva
In reply to this post by Frédéric Buclin

Quoting Frédéric Buclin <[hidden email]>:

> 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?
[...]

A long overdue task; go for it.

Cheers
Marcus

-
To view or change your list settings, click here:
<http://bugzilla.org/cgi-bin/mj_wwwusr?user=lists+s6506n84121h51@...>
Reply | Threaded
Open this post in threaded view
|

Re: Have a separate Bugzilla installation for the Bugzilla project?

Denis Roy
In reply to this post by Frédéric Buclin
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@...>
>
-
To view or change your list settings, click here:
<http://bugzilla.org/cgi-bin/mj_wwwusr?user=lists+s6506n84121h51@...>
Reply | Threaded
Open this post in threaded view
|

Re: Have a separate Bugzilla installation for the Bugzilla project?

Gervase Markham
In reply to this post by Frédéric Buclin
On 29/11/15 14:33, Frédéric Buclin wrote:
> I would suggest that
> the Bugzilla project has its own Bugzilla installation, managed by the
> upstream Bugzilla team itself.

I agree that now is the time for this, particularly given the very
generous offer from Denis and the Eclipse team.

Gerv

-
To view or change your list settings, click here:
<http://bugzilla.org/cgi-bin/mj_wwwusr?user=lists+s6506n84121h51@...>
Reply | Threaded
Open this post in threaded view
|

Re: Have a separate Bugzilla installation for the Bugzilla project?

Ryan Wilson-9
I'm definitely for this idea, maybe allocate it to bugs.bugzilla.org to cause the least confusion?

On Mon, Nov 30, 2015 at 9:20 AM, Gervase Markham <[hidden email]> wrote:
On 29/11/15 14:33, Frédéric Buclin wrote:
> I would suggest that
> the Bugzilla project has its own Bugzilla installation, managed by the
> upstream Bugzilla team itself.

I agree that now is the time for this, particularly given the very
generous offer from Denis and the Eclipse team.

Gerv

-
To view or change your list settings, click here:
<http://bugzilla.org/cgi-bin/mj_wwwusr?user=theycallmefish@...>

Reply | Threaded
Open this post in threaded view
|

Re: Have a separate Bugzilla installation for the Bugzilla project?

Dave Miller
In reply to this post by Gervase Markham
Gervase Markham wrote:
> On 29/11/15 14:33, Frédéric Buclin wrote:
>> I would suggest that
>> the Bugzilla project has its own Bugzilla installation, managed by the
>> upstream Bugzilla team itself.
>
> I agree that now is the time for this, particularly given the very
> generous offer from Denis and the Eclipse team.

I agree as well.  I was going to say that we probably ought to wait for
BMO to finish their current upstream merge and see where that puts us,
but I think the Eclipse offer gives us a pretty good excuse to do it
anyway :)  We have actually wanted it for a while, everyone's just
scared of the work involved in migrating.

--
Dave Miller http://www.justdave.net/
IT Infrastructure Engineer, Mozilla http://www.mozilla.org/
Project Leader, Bugzilla Bug Tracking System http://www.bugzilla.org/

-
To view or change your list settings, click here:
<http://bugzilla.org/cgi-bin/mj_wwwusr?user=lists+s6506n84121h51@...>
Reply | Threaded
Open this post in threaded view
|

Re: Have a separate Bugzilla installation for the Bugzilla project?

Frédéric Buclin
In reply to this post by Ryan Wilson-9
Le 30. 11. 15 17:31, Ryan Wilson a écrit :
> I'm definitely for this idea, maybe allocate it to bugs.bugzilla.org to
> cause the least confusion?

Yes, I agree. A much better name than bugzilla.bugzilla.org.

LpSolit

-
To view or change your list settings, click here:
<http://bugzilla.org/cgi-bin/mj_wwwusr?user=lists+s6506n84121h51@...>
Reply | Threaded
Open this post in threaded view
|

Re: Have a separate Bugzilla installation for the Bugzilla project?

Ryan Wilson-9
Should we run an implementation of Testopia on the new system, or would that go against the 'unmodified' state of this system? I'm willing to assist on that process.

On Mon, Nov 30, 2015 at 9:42 AM, Frédéric Buclin <[hidden email]> wrote:
Le 30. 11. 15 17:31, Ryan Wilson a écrit :
> I'm definitely for this idea, maybe allocate it to bugs.bugzilla.org to
> cause the least confusion?

Yes, I agree. A much better name than bugzilla.bugzilla.org.

LpSolit

-
To view or change your list settings, click here:
<http://bugzilla.org/cgi-bin/mj_wwwusr?user=theycallmefish@...>

Reply | Threaded
Open this post in threaded view
|

Re: Have a separate Bugzilla installation for the Bugzilla project?

Frédéric Buclin
Le 30. 11. 15 18:16, Ryan Wilson a écrit :
> Should we run an implementation of Testopia on the new system, or would
> that go against the 'unmodified' state of this system? I'm willing to
> assist on that process.


If we have a real use for Testopia (this would be a separate
discussion), it could be applied to the installation IMO. But in all
cases, I wouldn't do it till Testopia 3.0 is released (i.e. finish the
bug you are working on about killing all tr_*.cgi scripts) and till all
security bugs are fixed. (Bonus point for ExtJS -> jQuery)

LpSolit

-
To view or change your list settings, click here:
<http://bugzilla.org/cgi-bin/mj_wwwusr?user=lists+s6506n84121h51@...>
Reply | Threaded
Open this post in threaded view
|

Re: Have a separate Bugzilla installation for the Bugzilla project?

Denis Roy
In reply to this post by Dave Miller
If there's consensus, then I'd appreciate knowing what the project team
needs to run.

We use SuSE Linux Entreprise 12 which has everything needed to run a
Bugzilla instance.  Aside from the obvious Perl, MariaDB and other
related bits, what is needed in terms of hardware specs?

Denis


On 30/11/15 11:41 AM, Dave Miller wrote:

> Gervase Markham wrote:
>> On 29/11/15 14:33, Frédéric Buclin wrote:
>>> I would suggest that
>>> the Bugzilla project has its own Bugzilla installation, managed by the
>>> upstream Bugzilla team itself.
>> I agree that now is the time for this, particularly given the very
>> generous offer from Denis and the Eclipse team.
> I agree as well.  I was going to say that we probably ought to wait for
> BMO to finish their current upstream merge and see where that puts us,
> but I think the Eclipse offer gives us a pretty good excuse to do it
> anyway :)  We have actually wanted it for a while, everyone's just
> scared of the work involved in migrating.
>

-
To view or change your list settings, click here:
<http://bugzilla.org/cgi-bin/mj_wwwusr?user=lists+s6506n84121h51@...>
Reply | Threaded
Open this post in threaded view
|

Re: Have a separate Bugzilla installation for the Bugzilla project?

Dave Miller
In the grand scheme of things, the Bugzilla project is pretty small.  I
highly doubt we'd need anything more than a dual core server with 8GB of
RAM or so. (Maybe less RAM, depends on how bad mod_perl kills it, but
mod_perl is RAM-hungry).  Bugzilla.mozilla.org is a many-headed beast
because of Firefox and friends. :-)  Having the DB on a separate box
from the webserver may be good for performance.

Denis Roy wrote:

> If there's consensus, then I'd appreciate knowing what the project team
> needs to run.
>
> We use SuSE Linux Entreprise 12 which has everything needed to run a
> Bugzilla instance.  Aside from the obvious Perl, MariaDB and other
> related bits, what is needed in terms of hardware specs?
>
> Denis
>
>
> On 30/11/15 11:41 AM, Dave Miller wrote:
>> Gervase Markham wrote:
>>> On 29/11/15 14:33, Frédéric Buclin wrote:
>>>> I would suggest that
>>>> the Bugzilla project has its own Bugzilla installation, managed by the
>>>> upstream Bugzilla team itself.
>>> I agree that now is the time for this, particularly given the very
>>> generous offer from Denis and the Eclipse team.
>> I agree as well.  I was going to say that we probably ought to wait for
>> BMO to finish their current upstream merge and see where that puts us,
>> but I think the Eclipse offer gives us a pretty good excuse to do it
>> anyway :)  We have actually wanted it for a while, everyone's just
>> scared of the work involved in migrating.
>>
>
> -
> To view or change your list settings, click here:
> <http://bugzilla.org/cgi-bin/mj_wwwusr?user=justdave@...>

--
Dave Miller http://www.justdave.net/
IT Infrastructure Engineer, Mozilla http://www.mozilla.org/
Project Leader, Bugzilla Bug Tracking System http://www.bugzilla.org/

-
To view or change your list settings, click here:
<http://bugzilla.org/cgi-bin/mj_wwwusr?user=lists+s6506n84121h51@...>
Reply | Threaded
Open this post in threaded view
|

Re: Have a separate Bugzilla installation for the Bugzilla project?

Denis Roy
Thanks...  I have my plate busy with $DAY_JOB stuff but I expect to have
this going sometime next week.

Since this is the first ever vserver for a non-Eclipse project, we'll
set up a host on our DMZ, outside of our firewall.

Denis

On 12/02/2015 09:37 PM, Dave Miller wrote:

> In the grand scheme of things, the Bugzilla project is pretty small.  I
> highly doubt we'd need anything more than a dual core server with 8GB of
> RAM or so. (Maybe less RAM, depends on how bad mod_perl kills it, but
> mod_perl is RAM-hungry).  Bugzilla.mozilla.org is a many-headed beast
> because of Firefox and friends. :-)  Having the DB on a separate box
> from the webserver may be good for performance.
>
> Denis Roy wrote:
>> If there's consensus, then I'd appreciate knowing what the project team
>> needs to run.
>>
>> We use SuSE Linux Entreprise 12 which has everything needed to run a
>> Bugzilla instance.  Aside from the obvious Perl, MariaDB and other
>> related bits, what is needed in terms of hardware specs?
>>
>> Denis
>>
>>
>> On 30/11/15 11:41 AM, Dave Miller wrote:
>>> Gervase Markham wrote:
>>>> On 29/11/15 14:33, Frédéric Buclin wrote:
>>>>> I would suggest that
>>>>> the Bugzilla project has its own Bugzilla installation, managed by the
>>>>> upstream Bugzilla team itself.
>>>> I agree that now is the time for this, particularly given the very
>>>> generous offer from Denis and the Eclipse team.
>>> I agree as well.  I was going to say that we probably ought to wait for
>>> BMO to finish their current upstream merge and see where that puts us,
>>> but I think the Eclipse offer gives us a pretty good excuse to do it
>>> anyway :)  We have actually wanted it for a while, everyone's just
>>> scared of the work involved in migrating.
>>>
>>
>> -
>> To view or change your list settings, click here:
>> <http://bugzilla.org/cgi-bin/mj_wwwusr?user=justdave@...>
>
-
To view or change your list settings, click here:
<http://bugzilla.org/cgi-bin/mj_wwwusr?user=lists+s6506n84121h51@...>