diff options
| author | Nicolas Vigier <boklm@mageia.org> | 2013-04-14 13:46:12 +0000 |
|---|---|---|
| committer | Nicolas Vigier <boklm@mageia.org> | 2013-04-14 13:46:12 +0000 |
| commit | 1be510f9529cb082f802408b472a77d074b394c0 (patch) | |
| tree | b175f9d5fcb107576dabc768e7bd04d4a3e491a0 /zarb-ml/mageia-dev/2011-December/010350.html | |
| parent | fa5098cf210b23ab4f419913e28af7b1b07dafb2 (diff) | |
| download | archives-master.tar archives-master.tar.gz archives-master.tar.bz2 archives-master.tar.xz archives-master.zip | |
Diffstat (limited to 'zarb-ml/mageia-dev/2011-December/010350.html')
| -rw-r--r-- | zarb-ml/mageia-dev/2011-December/010350.html | 119 |
1 files changed, 119 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2011-December/010350.html b/zarb-ml/mageia-dev/2011-December/010350.html new file mode 100644 index 000000000..9f4c246d9 --- /dev/null +++ b/zarb-ml/mageia-dev/2011-December/010350.html @@ -0,0 +1,119 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] RFC: Opening Backports (once again...) + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20RFC%3A%20Opening%20Backports%20%28once%20again...%29&In-Reply-To=%3C201112111141.04611.anaselli%40linux.it%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="010328.html"> + <LINK REL="Next" HREF="010363.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] RFC: Opening Backports (once again...)</H1> + <B>Angelo Naselli</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20RFC%3A%20Opening%20Backports%20%28once%20again...%29&In-Reply-To=%3C201112111141.04611.anaselli%40linux.it%3E" + TITLE="[Mageia-dev] RFC: Opening Backports (once again...)">anaselli at linux.it + </A><BR> + <I>Sun Dec 11 11:41:02 CET 2011</I> + <P><UL> + <LI>Previous message: <A HREF="010328.html">[Mageia-dev] RFC: Opening Backports (once again...) +</A></li> + <LI>Next message: <A HREF="010363.html">[Mageia-dev] RFC: Opening Backports (once again...) +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#10350">[ date ]</a> + <a href="thread.html#10350">[ thread ]</a> + <a href="subject.html#10350">[ subject ]</a> + <a href="author.html#10350">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>sabato 10 dicembre 2011 alle 17:09, Thomas Backlund ha scritto: +><i> Sorry, buth this wont work in reality... +</I>><i> +</I>><i> Consider this: +</I>><i> +</I>><i> version X in Mageia 1 +</I>><i> version X+1 in Cauldron +</I>><i> +</I>><i> version X+1 gets backported. +</I>><i> +</I>><i> version X+2 uploaded in Cauldron +</I>><i> version X+2 cant be backported (depends on updated libs/packages in +</I>><i> Cauldron, and we dont backport libs that can break working setups) +</I>><i> +</I>><i> version X+1 in backports need to be fixed (security/maintenance fix) +</I>><i> (here your logic breaks down, there is no place to fix it) +</I>><i> +</I>><i> +</I>><i> And since we aim for quality backports, the maintainer may want to +</I>><i> stay with version X+1 in backports even if X+2 could be backported +</I>><i> if maintainer think X+2 isn't a good candidate for some reason. +</I> +So, couldn't we consider backports in the same way as updates? +The only difference is that they go into another branch, and they +need to have a higher version than in updates and lower than cauldron. + +Tests and validations follow the same rules, if a backport is not +validated won't be pushed. +Is that more work for QA? unfortunately yes, but i do hope tests +and validations can be done by more users interested in that +update/backport. + +Why using backports instead of updates then? because for some reasons +we -or maintainers- don't want to push as update a new version. +I'm not really in favour of a strict release update, we have already +pacakges not doing that (leaf ones, or those that are a pain to patch like +ff for instance,...). +In such a way backports is not going to be seen as a potential breakage of +the system, but as a part of distro life. + +A problem i can see though is if a maintainer decides that a version +that has been backported can become an update, even if it can be +managed by working on release version, that update is svn and HD room effect... + +Angelo + +-------------- next part -------------- +A non-text attachment was scrubbed... +Name: not available +Type: application/pgp-signature +Size: 198 bytes +Desc: This is a digitally signed message part. +URL: </pipermail/mageia-dev/attachments/20111211/665a6e8b/attachment.asc> +</PRE> + + + + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="010328.html">[Mageia-dev] RFC: Opening Backports (once again...) +</A></li> + <LI>Next message: <A HREF="010363.html">[Mageia-dev] RFC: Opening Backports (once again...) +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#10350">[ date ]</a> + <a href="thread.html#10350">[ thread ]</a> + <a href="subject.html#10350">[ subject ]</a> + <a href="author.html#10350">[ 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> |