[Mageia-dev] Updates and 0 release

[Samuel Verschelde]

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
> > 
> > Samuel Verschelde
> 
> 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

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

Samuel Verschelde