| Summary: | [RFE] Deploy Splinter add on to Red Hat's bugzilla | ||
|---|---|---|---|
| Product: | [Community] Bugzilla | Reporter: | Jiri Skala <jskala> |
| Component: | Attachments/Requests | Assignee: | PnT DevOps Devs <hss-ied-bugs> |
| Status: | CLOSED WONTFIX | QA Contact: | tools-bugs <tools-bugs> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 4.2 | CC: | aglotov, cmeadors, jingwang, jmcdonal, kbaker, mcepl |
| Target Milestone: | --- | Keywords: | FutureFeature, Reopened |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Enhancement | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2014-05-08 08:36:48 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Jiri Skala
2011-06-08 11:08:30 UTC
HI Jiri, The Splinter add on is part of bugzilla 4.0, So there is a big chance we will be including it in the bugzilla 4.0 upgrade. Cheers, Noura Hi Noura, thanks for info. Is there some time schedule for migration to BZ-4? Cheers, Jiri Hi Jiri, At this stage we don't really know when we will be migrating to BZ4.0.. but we are planning to do incremental updates to Redhat Bugzilla. Cheers, Noura Doing to set this up on a Brisbane virtual host for internal testing. -- simon The test server in comment #5 is well and truely gone (it went away last year). Since we have updated RHBZ to version 4.2, we would need to start again. (In reply to comment #7) > I've heard nothing about this in the past 15 months, and we are now > using Gerrit for code review. Could I ask for reconsidering this bug, please? Patch review is not useful for the internal RH purposes only, but there are tons of patches floating for the Fedora bugs and setting up proper gerrit repo for each package (actually for each patch) is too heavyweight. Encouraging code review by any means is always The Right Thing™ IMHO. Resetting to NEW since this isn't be worked on ATM. IMO we should not do this, there is already far too much load on our Bugzilla instance. If someone wants to pony up the dosh to build a serious web and database cluster then we could realistically look at doing this. In the absence of the three items requested above, I'm closing this RFE for now. Feel free to reopen if some or all of that information becomes available. As an aside, I'm interested in how many projects/users routinely exchange and/or review patches directly in Red Hat Bugzilla rather than using external tools like gerrit and github. |