summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/2011-July/007083.html
diff options
context:
space:
mode:
Diffstat (limited to 'zarb-ml/mageia-dev/2011-July/007083.html')
-rw-r--r--zarb-ml/mageia-dev/2011-July/007083.html158
1 files changed, 158 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2011-July/007083.html b/zarb-ml/mageia-dev/2011-July/007083.html
new file mode 100644
index 000000000..4852cb629
--- /dev/null
+++ b/zarb-ml/mageia-dev/2011-July/007083.html
@@ -0,0 +1,158 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+ <HEAD>
+ <TITLE> [Mageia-dev] Updates and 0 release
+ </TITLE>
+ <LINK REL="Index" HREF="index.html" >
+ <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Updates%20and%200%20release&In-Reply-To=%3C201107281008.44186.stormi%40laposte.net%3E">
+ <META NAME="robots" CONTENT="index,nofollow">
+ <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
+ <LINK REL="Previous" HREF="007080.html">
+ <LINK REL="Next" HREF="007086.html">
+ </HEAD>
+ <BODY BGCOLOR="#ffffff">
+ <H1>[Mageia-dev] Updates and 0 release</H1>
+ <B>Samuel Verschelde</B>
+ <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Updates%20and%200%20release&In-Reply-To=%3C201107281008.44186.stormi%40laposte.net%3E"
+ TITLE="[Mageia-dev] Updates and 0 release">stormi at laposte.net
+ </A><BR>
+ <I>Thu Jul 28 10:08:44 CEST 2011</I>
+ <P><UL>
+ <LI>Previous message: <A HREF="007080.html">[Mageia-dev] Updates and 0 release
+</A></li>
+ <LI>Next message: <A HREF="007086.html">[Mageia-dev] Updates and 0 release
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#7083">[ date ]</a>
+ <a href="thread.html#7083">[ thread ]</a>
+ <a href="subject.html#7083">[ subject ]</a>
+ <a href="author.html#7083">[ author ]</a>
+ </LI>
+ </UL>
+ <HR>
+<!--beginarticle-->
+<PRE>Le mercredi 27 juillet 2011 22:52:00, Samuel Verschelde a &#233;crit :
+&gt;<i> Le mercredi 27 juillet 2011 16:59:37, Samuel Verschelde a &#233;crit :
+</I>&gt;<i> &gt; Le mercredi 27 juillet 2011 12:52:04, Samuel Verschelde a &#233;crit :
+</I>&gt;<i> &gt; &gt; Le mardi 26 juillet 2011 19:38:30, Samuel Verschelde a &#233;crit :
+</I>&gt;<i> &gt; &gt; &gt; Le mardi 26 juillet 2011 18:42:05, Michael Scherer a &#233;crit :
+</I>&gt;<i> &gt; &gt; &gt; [snip]
+</I>&gt;<i> &gt; &gt; &gt;
+</I>&gt;<i> &gt; &gt; &gt; &gt; Yet, the problem would also be there for regular non-version
+</I>&gt;<i> &gt; &gt; &gt; &gt; upgrade ( ie, if we have foo-2-2.mga2 in cauldron and stable, and
+</I>&gt;<i> &gt; &gt; &gt; &gt; that we need to rebuild on stable and not on cauldron, we face the
+</I>&gt;<i> &gt; &gt; &gt; &gt; same problem ), so using 0 is a incomplete solution to the issue,
+</I>&gt;<i> &gt; &gt; &gt; &gt; and the only solution is to rebuild in cauldron, and such problem
+</I>&gt;<i> &gt; &gt; &gt; &gt; should better be detected by youri.
+</I>&gt;<i> &gt; &gt; &gt;
+</I>&gt;<i> &gt; &gt; &gt; Very good point, this is a decisive argument to me.
+</I>&gt;<i> &gt; &gt; &gt;
+</I>&gt;<i> &gt; &gt; &gt; &gt; So, the conclusion is that we should test ugprade rather than
+</I>&gt;<i> &gt; &gt; &gt; &gt; assuming that it will just work because we placed a 0 instead of a
+</I>&gt;<i> &gt; &gt; &gt; &gt; 1 somewhere.
+</I>&gt;<i> &gt; &gt; &gt;
+</I>&gt;<i> &gt; &gt; &gt; Ok for me provided we put in place the necessary processes to avoid
+</I>&gt;<i> &gt; &gt; &gt; upgrade problems (Youri::Submit::Test::Precedence for example).
+</I>&gt;<i> &gt; &gt; &gt;
+</I>&gt;<i> &gt; &gt; &gt; &gt; Now, using 0 prevent us from having a simple way of seeing what
+</I>&gt;<i> &gt; &gt; &gt; &gt; prerelease we ship and that should be updated to latest stable ( as
+</I>&gt;<i> &gt; &gt; &gt; &gt; this seems to me quite desirable ).
+</I>&gt;<i> &gt; &gt; &gt;
+</I>&gt;<i> &gt; &gt; &gt; Good point too.
+</I>&gt;<i> &gt; &gt; &gt;
+</I>&gt;<i> &gt; &gt; &gt; &gt; This is also inconsistent with the practice we had of backporting
+</I>&gt;<i> &gt; &gt; &gt; &gt; from cooker ( as the initial goal at Mandriva was to have 0
+</I>&gt;<i> &gt; &gt; &gt; &gt; modifications from cooker to backports to reduce the load ). And if
+</I>&gt;<i> &gt; &gt; &gt; &gt; we ship something in update and in backports, we would have the
+</I>&gt;<i> &gt; &gt; &gt; &gt; same packages with 2 different releases, and that doesn't seems a
+</I>&gt;<i> &gt; &gt; &gt; &gt; good idea.
+</I>&gt;<i> &gt; &gt; &gt;
+</I>&gt;<i> &gt; &gt; &gt; Worse, the backport would be preferred to the update :/
+</I>&gt;<i> &gt; &gt; &gt;
+</I>&gt;<i> &gt; &gt; &gt; You should have said all this right from the start rather than
+</I>&gt;<i> &gt; &gt; &gt; assuming that we would have all these elements in mind :)
+</I>&gt;<i> &gt; &gt; &gt;
+</I>&gt;<i> &gt; &gt; &gt; Samuel
+</I>&gt;<i> &gt; &gt;
+</I>&gt;<i> &gt; &gt; I suggest we add this point to tonight's meeting topics and that a
+</I>&gt;<i> &gt; &gt; decision be taken then.
+</I>&gt;<i> &gt; &gt;
+</I>&gt;<i> &gt; &gt; Then we would adapt the updates policy and the current packages in
+</I>&gt;<i> &gt; &gt; updates_testing if the 0 release in updates is abandoned. We must also
+</I>&gt;<i> &gt; &gt; decide if we continue to use subrels or not (using them could avoid
+</I>&gt;<i> &gt; &gt; unneeded rebuilds in cauldron when there are packaging bugs in
+</I>&gt;<i> &gt; &gt; updates).
+</I>&gt;<i> &gt; &gt;
+</I>&gt;<i> &gt; &gt; Best regards
+</I>&gt;<i> &gt; &gt;
+</I>&gt;<i> &gt; &gt; Samuel
+</I>&gt;<i> &gt;
+</I>&gt;<i> &gt; Ok, there will be no meeting tonight, so let's decide it on the ML. Was
+</I>&gt;<i> &gt; everyone convinced by misc's demonstration and do we agree to stop using
+</I>&gt;<i> &gt; the 0 release for updates and activate the
+</I>&gt;<i> &gt; Youri::Submit::Test::Precedence check on submit to prevent higher
+</I>&gt;<i> &gt; releases in mageia n than in mageia n+1 ?
+</I>&gt;<i> &gt;
+</I>&gt;<i> &gt; And if yes do we use subrels for subsequent modifications of packages
+</I>&gt;<i> &gt; that are proper to the mageia 1 branch ?
+</I>&gt;<i> &gt;
+</I>&gt;<i> &gt; I vote yes for both questions.
+</I>&gt;<i> &gt;
+</I>&gt;<i> &gt; Samuel
+</I>&gt;<i>
+</I>&gt;<i> Just to make things clear, contrarily as what was said in some of the
+</I>&gt;<i> previous mails, I was told on IRC by misc and dmorgan that we should
+</I>&gt;<i> always use subrels for updates.
+</I>&gt;<i>
+</I>&gt;<i> So this means that, when pushing foo-2-1.mga2 from cauldron to 1/updates,
+</I>&gt;<i> it will become foo-2-1.1.mga1 and not foo-2-1.mga1
+</I>&gt;<i>
+</I>&gt;<i> It means also that you will have to bump the release in cauldron in order
+</I>&gt;<i> to be allowed to submit the update, in that case. But as misc said, it
+</I>&gt;<i> should not happen very often :
+</I>&gt;<i> - providing new versions as updates should remain an exception per updates
+</I>&gt;<i> policy
+</I>&gt;<i> - if the package in cauldron already has a release &gt; 1, no need to bump it
+</I>&gt;<i>
+</I>&gt;<i> Hope it's clear.
+</I>&gt;<i>
+</I>&gt;<i> Best regards
+</I>&gt;<i>
+</I>&gt;<i> Samuel Verschelde
+</I>
+We have updates blocked by this release 0 issue, so we need a quick decision.
+I propose that if tomorrow nobody reacted against the proposal, it will be
+adopted.
+
+Best regards
+
+Samuel
+</PRE>
+
+
+
+
+
+
+
+
+<!--endarticle-->
+ <HR>
+ <P><UL>
+ <!--threads-->
+ <LI>Previous message: <A HREF="007080.html">[Mageia-dev] Updates and 0 release
+</A></li>
+ <LI>Next message: <A HREF="007086.html">[Mageia-dev] Updates and 0 release
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#7083">[ date ]</a>
+ <a href="thread.html#7083">[ thread ]</a>
+ <a href="subject.html#7083">[ subject ]</a>
+ <a href="author.html#7083">[ 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>