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