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

Angelo Naselli anaselli at linux.it
Fri Jun 8 13:31:30 CEST 2012

> If there is security issue then you have to fix it on cauldron too (usually with new
> version, so you can backport it to stable version). At least before release. And after
> backports are closed you can upgrade to latest stable version (for example mga3) and get
> patched version this way. I don't see the problem here.
Well I can't see how we can close a bp since we say we give 9 months of supporting version.
If we support bp, we also need to provides fixing at least. But i got your point, it's
a kind o release freeze for bp for the mga n-2.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: </pipermail/mageia-dev/attachments/20120608/f739e328/attachment.asc>

More information about the Mageia-dev mailing list