From 1be510f9529cb082f802408b472a77d074b394c0 Mon Sep 17 00:00:00 2001 From: Nicolas Vigier Date: Sun, 14 Apr 2013 13:46:12 +0000 Subject: Add zarb MLs html archives --- zarb-ml/mageia-dev/2011-July/007121.html | 115 +++++++++++++++++++++++++++++++ 1 file changed, 115 insertions(+) create mode 100644 zarb-ml/mageia-dev/2011-July/007121.html (limited to 'zarb-ml/mageia-dev/2011-July/007121.html') diff --git a/zarb-ml/mageia-dev/2011-July/007121.html b/zarb-ml/mageia-dev/2011-July/007121.html new file mode 100644 index 000000000..17a3733c2 --- /dev/null +++ b/zarb-ml/mageia-dev/2011-July/007121.html @@ -0,0 +1,115 @@ + + + + [Mageia-dev] Updates and 0 release + + + + + + + + + +

[Mageia-dev] Updates and 0 release

+ Samuel Verschelde + stormi at laposte.net +
+ Fri Jul 29 22:58:54 CEST 2011 +

+
+ +
Le vendredi 29 juillet 2011 22:45:41, Luis Daniel Lucio Quiroz a écrit :
+> Le Vendredi 29 Juillet 2011 22:16:26 Samuel Verschelde a écrit :
+> > Le jeudi 28 juillet 2011 10:08:44, Samuel Verschelde a écrit :
+> > > Le mercredi 27 juillet 2011 22:52:00, Samuel Verschelde a écrit :
+> > > > Le mercredi 27 juillet 2011 16:59:37, Samuel Verschelde a écrit :
+> > > > > Ok, there will be no meeting tonight, so let's decide it on the
+> > > > > ML. Was everyone convinced by misc's demonstration and do we
+> > > > > agree to stop using the 0 release for updates and activate the
+> > > > > Youri::Submit::Test::Precedence check on submit to prevent
+> > > > > higher
+> > > > > releases in mageia n than in mageia n+1 ?
+> > > > > 
+> > > > > And if yes do we use subrels for subsequent modifications of
+> > > > > packages
+> > > > > that are proper to the mageia 1 branch ?
+> > > > > 
+> > > > > I vote yes for both questions.
+> > > > > 
+> > > > > Samuel
+> > > > 
+> > > > Just to make things clear, contrarily as what was said in some of
+> > > > the
+> > > > previous mails, I was told on IRC by misc and dmorgan that we should
+> > > > always use subrels for updates.
+> > > > 
+> > > > So this means that, when pushing foo-2-1.mga2 from cauldron to
+> > > > 1/updates, it will become foo-2-1.1.mga1 and not foo-2-1.mga1
+> > > > 
+> > > > It means also that you will have to bump the release in cauldron in
+> > > > order to be allowed to submit the update, in that case. But as misc
+> > > > said, it should not happen very often :
+> > > > - providing new versions as updates should remain an exception per
+> > > > updates policy
+> > > > - if the package in cauldron already has a release > 1, no need to
+> > > > bump
+> > > > it
+> > > > 
+> > > > Hope it's clear.
+> > > > 
+> > > > Best regards
+> > > > 
+> > > 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
+> > > 
+> > As promised, I'm going to update the updates policy regarding release and
+> > to fix the release for updates currently staging in updates_testing when
+> > they need to.
+> > 
+> > Best regards
+> > 
+> Can you plaste the URL please?
+
+http://www.mageia.org/wiki/doku.php?id=updates_policy
+
+Samuel
+
+ + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ -- cgit v1.2.1