diff options
Diffstat (limited to 'zarb-ml/mageia-dev/2011-June/006075.html')
| -rw-r--r-- | zarb-ml/mageia-dev/2011-June/006075.html | 135 |
1 files changed, 135 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2011-June/006075.html b/zarb-ml/mageia-dev/2011-June/006075.html new file mode 100644 index 000000000..786a02731 --- /dev/null +++ b/zarb-ml/mageia-dev/2011-June/006075.html @@ -0,0 +1,135 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Proposal of a backporting process + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proposal%20of%20a%20backporting%20process&In-Reply-To=%3C4E0931D5.8050704%40laposte.net%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="006017.html"> + <LINK REL="Next" HREF="006018.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Proposal of a backporting process</H1> + <B>andre999</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proposal%20of%20a%20backporting%20process&In-Reply-To=%3C4E0931D5.8050704%40laposte.net%3E" + TITLE="[Mageia-dev] Proposal of a backporting process">andr55 at laposte.net + </A><BR> + <I>Tue Jun 28 03:43:49 CEST 2011</I> + <P><UL> + <LI>Previous message: <A HREF="006017.html">[Mageia-dev] Proposal of a backporting process +</A></li> + <LI>Next message: <A HREF="006018.html">[Mageia-dev] Proposal of a backporting process +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#6075">[ date ]</a> + <a href="thread.html#6075">[ thread ]</a> + <a href="subject.html#6075">[ subject ]</a> + <a href="author.html#6075">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Samuel Verschelde a écrit : +><i> +</I>><i> Le vendredi 24 juin 2011 21:39:51, Ahmad Samir a écrit : +</I>>><i> On 24 June 2011 02:09, Michael Scherer<<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">misc at zarb.org</A>> wrote: +</I> +... + +>>><i> - I am not sure on this part, but basically, we have 2 choices : +</I>>>><i> - the packager take the cauldron package and push to backport testing +</I>>>><i> - the packager move the cauldron package in svn to backport, and there +</I>>>><i> send it to backport testing. +</I>>>><i> +</I>>>><i> Proposal 1 mean less work duplication, but proposal 2 let us do more +</I>>>><i> customization. +</I>>><i> +</I>>><i> Option 1 doesn't only mean not duplicating work, but also that the the +</I>>><i> spec in backports svn isn't ever out-dated; the only reason I see a +</I>>><i> package being in stable distro SVN is if it's in /release|updates, not +</I>>><i> backports... +</I>><i> +</I>><i> I'm not sure I understand your point. What do you mean with out-dated specs in +</I>><i> backports ? +</I>><i> I favor option 2 (with all needed useful shortcuts in mgarepo and BS to make +</I>><i> it simple for packagers) because it allows to cope with the following +</I>><i> situation : +</I>><i> - foo is in version 1.2.2 in release|updates +</I>><i> - foo is in version 2.0alpha in cauldron, full of bugs but hopefully ready for +</I>><i> the next stable release +</I>><i> - the latest release in the 1.x branch, 1.3.0, brings many features requested +</I>><i> by some users, we want to provide it as a backport : with option 1 we can't, +</I>><i> with option 2 we can. +</I>><i> +</I>><i> or : +</I>><i> - foo is in version 1.2.2 in release|updates +</I>><i> - foo is in version 2.0alpha in cauldron, full of bugs but hopefully ready for +</I>><i> the next stable release +</I>><i> - we had backported version 1.2.6 before switching to 2.0alpha in cauldron +</I>><i> - the backported version 1.2.6 has a big bug we hadn't spotted during tests +</I>><i> and we want to fix in the backport : with option 1 we can't, with option 2 we +</I>><i> can. +</I>><i> +</I>><i> So, for me, this is definitely option 2. +</I> +Given this explanation, I would definitely go for option 2 as well. + +><i> However, I think it must be made a painless as possible to packagers : +</I>><i> - in the common case, allow to submit directly from cauldron to the backports +</I>><i> media, but let the BS detect that and automatically do the SVN copy part. +</I>><i> - for the situations I described above, work with the backport branch +</I>><i> similarly as we work on updates (technically speaking : SVN, BS...). +</I> +Sound good to me. + +>>><i> if the package doesn't build, the packager fix ( or drop the idea if +</I>>>><i> this requires too much work ) +</I>>>><i> +</I>>>><i> - the packager send requesting feedback about the backport from the +</I>>>><i> people who requested it, and test it as well. +</I>>><i> +</I>>><i> Probably off-topic, but how will that work with madb? i.e. how will +</I>>><i> the maintainer get the feedback? +</I>><i> +</I>><i> I partially answered above : either via bugzilla, or via a simple tracking +</I>><i> system included in madb for that need. It will depend on the chosen process, +</I>><i> we'll try to adapt the tool to the situation. +</I> +I tend to like the idea of using bugzilla with a streamlined template, to avoid +unnecessary duplication of code to be maintained. +But if madb can track things better, and it can be readily developed, that sounds good. +As for packagers, it shouldn't make much difference if the tools are done right. + +><i> Best regards +</I>><i> +</I>><i> Samuel Verschelde +</I> +Regards + +-- +André +</PRE> + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="006017.html">[Mageia-dev] Proposal of a backporting process +</A></li> + <LI>Next message: <A HREF="006018.html">[Mageia-dev] Proposal of a backporting process +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#6075">[ date ]</a> + <a href="thread.html#6075">[ thread ]</a> + <a href="subject.html#6075">[ subject ]</a> + <a href="author.html#6075">[ author ]</a> + </LI> + </UL> + +<hr> +<a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More information about the Mageia-dev +mailing list</a><br> +</body></html> |