[Mageia-dev] Backports policy clarification (and discussion)

Angelo Naselli anaselli at linux.it
Sat Jun 9 21:34:34 CEST 2012

Hash: SHA1

Il 09/06/2012 20:38, Sander Lepik ha scritto:
> I see backports as the way to get some new stuff from cauldron
> before cauldron is fully stable. There is no point to backport from
> cauldron to n-2 (mga1 at the moment). If the user wants so much
> newer stuff s/he better upgrade to latest stable.
There could be no point now -and maybe for you-, but it could be in
future or for sombody who does not want to update to mga2 yet (kmail2,
akonadi, kwallet issues) and want to get some leaf packages for his/her
needs (firefox, mondevelop, ...).
If we allow bp, and i'm in favor of that, we must consider all the
possible cases, and must be able to upgrade to next mgaX without
issues due to bp imho.

> Cherry-picking for me means that i can upgrade some packages from
> backports and then disable the repo. After that i'm still able to
> upgrade to fully stable next release (w/o backports).
I understood that also, and it should work exactly as we are using
XXX_testing for some packages, if bp is approved must
work as expected and allow either upgrade or disabling bp.

Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/


More information about the Mageia-dev mailing list