diff options
Diffstat (limited to 'zarb-ml/mageia-sysadm/2012-June/004477.html')
| -rw-r--r-- | zarb-ml/mageia-sysadm/2012-June/004477.html | 123 |
1 files changed, 123 insertions, 0 deletions
diff --git a/zarb-ml/mageia-sysadm/2012-June/004477.html b/zarb-ml/mageia-sysadm/2012-June/004477.html new file mode 100644 index 000000000..d8c2d8f24 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2012-June/004477.html @@ -0,0 +1,123 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-sysadm] New Bugzilla maintainer? + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-sysadm%40mageia.org?Subject=Re%3A%20%5BMageia-sysadm%5D%20New%20Bugzilla%20maintainer%3F&In-Reply-To=%3C20120611182905.GR21938%40mars-attacks.org%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="004473.html"> + <LINK REL="Next" HREF="004478.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-sysadm] New Bugzilla maintainer?</H1> + <B>nicolas vigier</B> + <A HREF="mailto:mageia-sysadm%40mageia.org?Subject=Re%3A%20%5BMageia-sysadm%5D%20New%20Bugzilla%20maintainer%3F&In-Reply-To=%3C20120611182905.GR21938%40mars-attacks.org%3E" + TITLE="[Mageia-sysadm] New Bugzilla maintainer?">boklm at mars-attacks.org + </A><BR> + <I>Mon Jun 11 20:29:05 CEST 2012</I> + <P><UL> + <LI>Previous message: <A HREF="004473.html">[Mageia-sysadm] New Bugzilla maintainer? +</A></li> + <LI>Next message: <A HREF="004478.html">[Mageia-sysadm] New Bugzilla maintainer? +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#4477">[ date ]</a> + <a href="thread.html#4477">[ thread ]</a> + <a href="subject.html#4477">[ subject ]</a> + <a href="author.html#4477">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>On Mon, 11 Jun 2012, Marja van Waes wrote: + +><i> Hi everyone, +</I>><i> +</I>><i> Frédéric Buclin is willing to become our new Bugzilla maintainer :) +</I>><i> +</I>><i> D. Morgan said he is not against that, and that we could talk about it +</I>><i> today. +</I>><i> +</I>><i> A bit more about Frédéric (LpSolit) for who doesn't know him: +</I>><i> He maintains GCC Bugzilla, is part of the upstream Bugzilla team and has +</I>><i> always been very willing to help us with advice on Bugzilla issues. +</I>><i> +</I>><i> Frédéric has explained that his offer is only valid if he can use the +</I>><i> upstream code from bzr, not the Bugzilla RPM. If that's not possible, then +</I>><i> he is not interested in maintaining it, because, in his words: "A RPM is +</I>><i> always behind, has its own hacks, and upstream patches cannot be applied as +</I>><i> is." +</I>><i> +</I>><i> I told him I can understand something like our different setup (see the +</I>><i> .spec of our Bugzilla package) wouldn't make life easier: he'd have to be +</I>><i> aware when working on the Mageia Bugzilla and forget when working on GCC +</I>><i> bugzilla or doing things upstream. +</I>><i> +</I>><i> He then added: +</I>><i> +</I>><i> "Not only that, but every time we update the Bugzilla RPM, customizations +</I>><i> made to Mageia Bugzilla would be lost, while bzr is able to apply changes +</I>><i> without altering customizations (unless they heavily conflict, of course)." +</I>><i> +</I>><i> I asked Nicolas about sysadmin policies that might apply and he answered +</I>><i> that there isn't a rule for everything, but that things are discussed on +</I>><i> the ml before being done. +</I> +You are only quoting a small part of what I said. I also said I don't +think we should stop using an RPM package to setup the bugzilla. + +I think we should continue using puppet and an RPM package to setup our +bugzilla : + - Current setup is working fine, and puppet or RPM is not what is + blocking upgrade I think. What is (or was) blocking upgrade is update + of our bugzilla templates to bugzilla 4 (already done by dmorgan + 4 months ago), and testing in a VM to test database migration and check + that everything is still working. We could have done the upgrade 4 months + ago, but it was decided to wait after Mageia 2 release to avoid adding + problems just before release. + - We already have a package for bugzilla in Mageia maintained by Olav, + and it is not behind, it is the latest stable release. + - We can apply upstream patches in the package if needed + - Local customizations are lost when we update the package, but I think + we don't want local customizations on the server. If we need + customizations we can add them as a patch to the package. And I think + it should be possible to maintain that patch using bzr. We can use a + custom package for our bugzilla if necessary. + - Using our package helps find problems in the package, which should + also benefits to other users of the package on Mageia. + +But help from Frédéric is welcome to improve Mageia bugzilla, give +advices, patches, plugins, etc ... And should be easier once we have +migrated to version 4.2. Maybe we can setup a VM to help testing of +bugzilla changes before they are applied to the server. Or use vagrant +or other similar tool. + +</PRE> + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="004473.html">[Mageia-sysadm] New Bugzilla maintainer? +</A></li> + <LI>Next message: <A HREF="004478.html">[Mageia-sysadm] New Bugzilla maintainer? +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#4477">[ date ]</a> + <a href="thread.html#4477">[ thread ]</a> + <a href="subject.html#4477">[ subject ]</a> + <a href="author.html#4477">[ author ]</a> + </LI> + </UL> + +<hr> +<a href="https://www.mageia.org/mailman/listinfo/mageia-sysadm">More information about the Mageia-sysadm +mailing list</a><br> +</body></html> |