[Mageia-dev] Updates and 0 release

[Samuel Verschelde]

Le mardi 26 juillet 2011 18:42:05, Michael Scherer a écrit :
[snip]
> 
> Yet, the problem would also be there for regular non-version upgrade
> ( ie, if we have foo-2-2.mga2 in cauldron and stable, and that we need
> to rebuild on stable and not on cauldron, we face the same problem ), so
> using 0 is a incomplete solution to the issue, and the only solution is
> to rebuild in cauldron, and such problem should better be detected by
> youri.

Very good point, this is a decisive argument to me.

> 
> So, the conclusion is that we should test ugprade rather than assuming
> that it will just work because we placed a 0 instead of a 1 somewhere.

Ok for me provided we put in place the necessary processes to avoid upgrade 
problems (Youri::Submit::Test::Precedence for example).

> 
> Now, using 0 prevent us from having a simple way of seeing what
> prerelease we ship and that should be updated to latest stable ( as this
> seems to me quite desirable ).

Good point too.

> 
> This is also inconsistent with the practice we had of backporting from
> cooker ( as the initial goal at Mandriva was to have 0 modifications
> from cooker to backports to reduce the load ). And if we ship something
> in update and in backports, we would have the same packages with 2
> different releases, and that doesn't seems a good idea.

Worse, the backport would be preferred to the update :/

You should have said all this right from the start rather than assuming that 
we would have all these elements in mind :)

Samuel