[Mageia-dev] Backports policy clarification (and discussion)
anaselli at linux.it
Sat Jun 9 21:26:17 CEST 2012
-----BEGIN PGP SIGNED MESSAGE-----
Il 09/06/2012 12:39, Thomas Backlund ha scritto:
>> OK. To backport from Cauldron to mga1, we have to backport from
>>> Cauldron to mga2, (bumping the revision in cauldron to ensure
>>> that is is higher), then backport from mga2 to mga1, ensuring
>>> that the revision is lower in mga1 than in mga2. (e.g.
>>> revision x.1 in cauldron, x.0.1 in mga2, x.0.0.1 in mga1)
>>> Pretty straight forward.
> Not needed as 1.mgaX > 1.mga3 > 1.mga2 > 1.mga1
IIUC the only problem is when in the above situation
we have 1.1.mga1 for any reasons (bug fixing for instance, maybe not
needed in any mgaX > mga1).
I believe in that situation who makes the bug-fixing has to work on
other back-ports/updates because in mgaX > mga1 that package could be
in core and not in bp.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
-----END PGP SIGNATURE-----
More information about the Mageia-dev