Open
Bug 127876
Opened 23 years ago
Updated 2 years ago
Bugzilla installation for Bugzilla bugs (dogfood)
Categories
(Bugzilla :: bugzilla.org, enhancement, P3)
Bugzilla
bugzilla.org
Tracking
()
REOPENED
People
(Reporter: myk, Unassigned)
References
(Depends on 5 open bugs)
Details
(Keywords: dogfood)
A separate Bugzilla installation running the latest Bugzilla development code should be set up for the Bugzilla product currently hosted on b.m.o. This would give us a good way to test upgrades to Bugzilla before installing them on b.m.o. and give developers a much tighter feedback loop for their changes to make it easier to spot and fix regressions.
Reporter | ||
Updated•23 years ago
|
Updated•18 years ago
|
Keywords: dogfood
Summary: Bugzilla installation for Bugzilla bugs → Bugzilla installation for Bugzilla bugs (dogfood)
Comment 1•18 years ago
|
||
This is going to be a priority for the Bugzilla project again, our development cycle is getting hurt too badly by not having an installation running the tip that everyone actually uses.
Assignee: myk → justdave
Updated•18 years ago
|
Priority: -- → P3
Comment 2•18 years ago
|
||
Is this a problem anymore? bmo uses tip now. :)
Comment 3•18 years ago
|
||
(In reply to comment #2) > Is this a problem anymore? bmo uses tip now. :) This will be a problem as relatively soon unless bmo's admins and userbase are willing to keep it running tip. Also all of the blockers are important for bugzilla in general, even this bug is WONTFIXed.
Updated•18 years ago
|
QA Contact: myk → reed
Comment 4•16 years ago
|
||
Rearranging this component to not have me as the default assignee, so that it doesn't appear like I'm intending to work on bugs that other people could be taking care of if they didn't think I was already doing them. If this bug is a software issue on b.m.o and you'd like to fix it, the modified source is now available for the patching (see bug 373688). Reassigning to the new default owner.
Assignee: justdave → nobody
QA Contact: reed → other-bmo-issues
Comment 5•15 years ago
|
||
justdave: are there any current plans to do this? We seem to have managed without this since 2002, and the b.m.o. version is now available for anyone to pull and test via bzr. Gerv
Comment 6•15 years ago
|
||
There are still plans to do this, but we would need to resolve all of the blockers nicely, first.
Comment 7•15 years ago
|
||
Personally, this is WONTFIX. We have QA installations to catch main bugs, and I wouldn't want to use tip code for our main installation.
Updated•13 years ago
|
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → WONTFIX
Updated•13 years ago
|
Component: Bugzilla: Other b.m.o Issues → General
Product: mozilla.org → bugzilla.mozilla.org
Comment 8•9 years ago
|
||
(In reply to Frédéric Buclin from comment #7) > Personally, this is WONTFIX. We have QA installations to catch main bugs, > and I wouldn't want to use tip code for our main installation. I changed my mind since I wrote this. In 2009, BMO codebase was close from upstream Bugzilla, and they were upgrading pretty "frequently", making the needs for a separate Bugzilla installation useless. Now, BMO differs more and more from what upstream Bugzilla looks like, including the backend code. BMO admins also remove some features which exist upstream, such as bug 1227316, and I strongly think that running a separate Bugzilla installation which would stay in sync with master (probably upgraded manually if the code becomes unstable for a few weeks due to major breaking changes) would help to let users discover new features and devs to find regressions.
Whiteboard: WONTFIX?
Huge +1 from me. Eclipse is willing to allocate servers and ongoing sysadmin time to help make this happen.
Assignee: nobody → website
Status: RESOLVED → REOPENED
Component: General → bugzilla.org
Product: bugzilla.mozilla.org → Bugzilla
QA Contact: default-qa
Resolution: WONTFIX → ---
Version: other → unspecified
You need to log in
before you can comment on or make changes to this bug.
Description
•