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/2012-June/016874.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/2012-June/016874.html')
| -rw-r--r-- | zarb-ml/mageia-dev/2012-June/016874.html | 250 |
1 files changed, 250 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2012-June/016874.html b/zarb-ml/mageia-dev/2012-June/016874.html new file mode 100644 index 000000000..73b84162d --- /dev/null +++ b/zarb-ml/mageia-dev/2012-June/016874.html @@ -0,0 +1,250 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Backports Summary + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Backports%20Summary&In-Reply-To=%3C4FEABA98.2060700%40laposte.net%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="016857.html"> + <LINK REL="Next" HREF="016899.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Backports Summary</H1> + <B>andre999</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Backports%20Summary&In-Reply-To=%3C4FEABA98.2060700%40laposte.net%3E" + TITLE="[Mageia-dev] Backports Summary">andre999mga at laposte.net + </A><BR> + <I>Wed Jun 27 09:47:36 CEST 2012</I> + <P><UL> + <LI>Previous message: <A HREF="016857.html">[Mageia-dev] Backports Summary +</A></li> + <LI>Next message: <A HREF="016899.html">[Mageia-dev] Backports Summary +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#16874">[ date ]</a> + <a href="thread.html#16874">[ thread ]</a> + <a href="subject.html#16874">[ subject ]</a> + <a href="author.html#16874">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Thomas Backlund a écrit : +><i> Thomas Backlund skrev 26.6.2012 22:25: +</I>>><i> So, +</I>>><i> we have been discussing this many times, and not gotten any +</I>>><i> satisfactory decision to go ahead yet... +</I>>><i> +</I>>><i> +</I>>><i> +</I>>><i> First off, we decided long ago that backports will be +</I>>><i> better supported than during mdv times, meaning security +</I>>><i> and bugfixes and has to pass QA. +</I>>><i> +</I>>><i> +</I>>><i> +</I>>><i> Now for references: +</I>>><i> * we have the backports policy: +</I>>><i> <A HREF="https://wiki.mageia.org/en/Backports_policy">https://wiki.mageia.org/en/Backports_policy</A> +</I>>><i> +</I>>><i> * Last discussions started by Stormi: +</I>>><i> * [Mageia-dev] Backports policy clarification (and discussion) +</I>>><i> <A HREF="https://www.mageia.org/pipermail/mageia-dev/2012-June/016265.html">https://www.mageia.org/pipermail/mageia-dev/2012-June/016265.html</A> +</I>>><i> +</I>>><i> * [Mageia-dev] Proposed Feature:Backports_update_applet +</I>>><i> <A HREF="https://www.mageia.org/pipermail/mageia-dev/2012-June/016263.html">https://www.mageia.org/pipermail/mageia-dev/2012-June/016263.html</A> +</I>>><i> +</I>>><i> * It also came up in the discussion about fixing bug 2317: +</I>>><i> * [Mageia-dev] bug 2317 revisited: --update option should behave +</I>>><i> like +</I>>><i> --search-media +</I>>><i> <A HREF="https://www.mageia.org/pipermail/mageia-dev/2012-June/016692.html">https://www.mageia.org/pipermail/mageia-dev/2012-June/016692.html</A> +</I>>><i> +</I>>><i> +</I>>><i> People seem to agree on most things, but there is a few questions +</I>>><i> that need to be decided how to handle. +</I>>><i> +</I>>><i> +</I>>><i> +</I>>><i> +</I>>><i> Lets start with the summary and suggestion of how to get it started: +</I>>><i> (addendum / refinements / important points of current backports policy) +</I>>><i> +</I>>><i> * backports is supported as long as the rest of the release +</I>>><i> * packages must always be in cauldron first +</I>>><i> * if you want to backport a package someone else is maintainer +</I>>><i> for, you need to discuss with maintainer first. if he dont +</I>>><i> want the package to be backported _and_ have valid reasons, +</I>>><i> respect that. (if you disagree, you can still ask council) +</I>>><i> * if you backport anything, (regardless if you are the real +</I>>><i> maintainer or not) you accept the responsibility of +</I>>><i> handling the bugreports against the backport and make sure +</I>>><i> it gets patched (or upgraded) to get security fixes. +</I>>><i> * cherrypicking backports must work, so requires need +</I>>><i> to be checked and be strict to make sure they work +</I>>><i> * nothing in backports must require the use of "--nodeps" +</I>>><i> or "--force" to get it to install +</I>>><i> * QA will do basic tests to make sure it works and obeys the rules +</I>>><i> * QA can deny package(s) to be backported if it breaks the policy +</I>>><i> * QA has /updates as priority, and /backports will be handled +</I>>><i> if/when there is time, so if you want faster response, join QA +</I>>><i> to help out with the workload. +</I>>><i> +</I>>><i> +</I>>><i> +</I>>><i> Now a point that got raised during discussion of bug 2317: +</I>>><i> * if a backport break because of something ending up in /updates +</I>>><i> it's a bug to be reported against the backport (and not against +</I>>><i> the released update) as packages ending up in /updates are only +</I>>><i> validated against /release and /updates (and rightfully so as +</I>>><i> thats how they are built too) +</I>>><i> +</I>>><i> +</I>>><i> +</I>>><i> And some important points to avoid making backports_testing a +</I>>><i> "dumping ground" for package(r)s trying to avoid the policy: +</I>>><i> * after submitting anything to backports_testing you have +</I>>><i> 48 hours to file/assign a "Backport to validate" at +</I>>><i> bugs.mageia.org. +</I>>><i> * package needs to be validated within 1 month (or shorter/longer +</I>>><i> time if QA wants that) +</I>>><i> * failure to match any of the two timelimits will get the +</I>>><i> package removed from updates_testing again. (I understand this +</I>><i> +</I>><i> This should have stated "backports_testing" +</I>><i> +</I>>><i> will get some questions, but if we cant get people to help out +</I>>><i> with QA we might as well never open backports) +</I>>><i> +</I>>><i> +</I>>><i> +</I>>><i> And then the questions we need to decide on: +</I>>><i> (substitute mga1/mga2 for any future release...) +</I>>><i> 1. Do we support backporting package with higher version +</I>>><i> than package in the following next mageia release has ? +</I>>><i> (meaning if mga1 has v12, and mga2 has v14, is it ok +</I>>><i> to backport v16 to mga1?) +</I>>><i> * PRO: more uptodate package in backports +</I>>><i> * CON: can cause trouble during distro upgrade +</I>>><i> * imho both technically ok as long as we make sure +</I>>><i> its documented so people know what to expect. +</I>>><i> +</I>>><i> 2. If one want to backport a package to mga1, does it mean +</I>>><i> it must be backported to mga2 in order to preserve +</I>>><i> upgrade path (unless already in mga2, depending on +</I>>><i> question 1)? +</I>>><i> +</I>>><i> +</I>>><i> +</I>>><i> And since we can continue this what/if discussion forever, +</I>>><i> and thereby delay backports even more here is my take on it: +</I>>><i> +</I>>><i> my suggestions to decide on question 1 and 2: +</I>>><i> 1. backporting bigger version to mga1 than mga2 has is +</I>>><i> allowed as it will otherwise restrict backporting +</I>>><i> too much. (and since its leaf packages, it should +</I>>><i> not break (too much)). Lets just make it clear to +</I>>><i> everyone using backports. +</I>>><i> +</I>>><i> 2. we cant really require that as the one backporting +</I>>><i> the package to mga1 has to backport it to mga2 too +</I>>><i> as he/she might not be using mga2 at all. if someone +</I>>><i> wants/needs the backport for mga2, they need to +</I>>><i> request that. (in reality, going by how backports +</I>>><i> got handled in mdv most backports will end up in +</I>>><i> all supported releases anyway) +</I> +I would favour adding the requirement that the dependancies of the +backport must be available in the next release. So that we would expect +that the backport would continue to function properly on an update to +the next release, but we don't require that it be tested, so it may not. +This is a relatively simple to check, so it won't have a big impact on +QA, but should increase significantly the reliability of backports. + +>><i> If we can agree on this as a start, we can open backports +</I>>><i> soon so we get actual facts of how backports policy and +</I>>><i> process works. +</I>>><i> +</I>>><i> Then we rewiew backports policy and process in ~6 months, +</I>>><i> and adjust it if needed. +</I>>><i> +</I>>><i> +</I>>><i> +</I>>><i> Comments? Questions ? +</I> +I would favour tagging backports as update repos, so that in the event +of a newer backport for security or bug fixes, that it will be +automatically presented with other updates. +This would require some modification to update tools, so it seems to me +ok to open backports beforehand, with the understanding that the update +tools would be changed to accommodate this. +>><i> -- +</I>>><i> +</I>>><i> Thomas +</I>>><i> . +</I>>><i> +</I>-- +André + +</PRE> + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="016857.html">[Mageia-dev] Backports Summary +</A></li> + <LI>Next message: <A HREF="016899.html">[Mageia-dev] Backports Summary +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#16874">[ date ]</a> + <a href="thread.html#16874">[ thread ]</a> + <a href="subject.html#16874">[ subject ]</a> + <a href="author.html#16874">[ 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> |