From 1be510f9529cb082f802408b472a77d074b394c0 Mon Sep 17 00:00:00 2001 From: Nicolas Vigier <boklm@mageia.org> Date: Sun, 14 Apr 2013 13:46:12 +0000 Subject: Add zarb MLs html archives --- .../20120608/7e8c5812/attachment-0001.html | 25 ++++++++++++++++++++++ .../attachments/20120608/7e8c5812/attachment.html | 25 ++++++++++++++++++++++ 2 files changed, 50 insertions(+) create mode 100644 zarb-ml/mageia-dev/attachments/20120608/7e8c5812/attachment-0001.html create mode 100644 zarb-ml/mageia-dev/attachments/20120608/7e8c5812/attachment.html (limited to 'zarb-ml/mageia-dev/attachments/20120608/7e8c5812') diff --git a/zarb-ml/mageia-dev/attachments/20120608/7e8c5812/attachment-0001.html b/zarb-ml/mageia-dev/attachments/20120608/7e8c5812/attachment-0001.html new file mode 100644 index 000000000..8b6981e38 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20120608/7e8c5812/attachment-0001.html @@ -0,0 +1,25 @@ +<p>On Jun 8, 2012 2:33 PM, "Samuel Verschelde" <<a href="mailto:stormi@laposte.net">stormi@laposte.net</a>> wrote:<br> +><br> +> Le vendredi 8 juin 2012 11:40:59, Sander Lepik a écrit :<br> +> > 08.06.2012 11:51, Samuel Verschelde kirjutas:<br> +> > > And what about security issues and bugs to those backports? It will use<br> +> > > more packager ressource to patch backports than to provide newer<br> +> > > versions, won't it?<br> +> ><br> +> > If there is security issue then you have to fix it on cauldron too (usually<br> +> > with new version, so you can backport it to stable version). At least<br> +> > before release. And after backports are closed you can upgrade to latest<br> +> > stable version (for example mga3) and get patched version this way. I<br> +> > don't see the problem here.<br> +> ><br> +><br> +> So you mean that backports are supported for 9 months and then you have to<br> +> upgrade to the next Mageia if you want security fixes... That's not what I call<br> +> support :/ What about people who want not to upgrade their whole system to the<br> +> next Mageia and still get support for that backport they installed?<br> +I don't think that we need to support backports that much. It should be clear that backports might not get all security updates. We should guarantee that it's possible to upgrade to next stable release and that's about it. We really don't have resources for more.<br> + +And if user doesn't want to upgrade to next release but at the same time wants security updates s/he can always downgrade.</p> +<p>--<br> +Sander<br> +</p> diff --git a/zarb-ml/mageia-dev/attachments/20120608/7e8c5812/attachment.html b/zarb-ml/mageia-dev/attachments/20120608/7e8c5812/attachment.html new file mode 100644 index 000000000..8b6981e38 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20120608/7e8c5812/attachment.html @@ -0,0 +1,25 @@ +<p>On Jun 8, 2012 2:33 PM, "Samuel Verschelde" <<a href="mailto:stormi@laposte.net">stormi@laposte.net</a>> wrote:<br> +><br> +> Le vendredi 8 juin 2012 11:40:59, Sander Lepik a écrit :<br> +> > 08.06.2012 11:51, Samuel Verschelde kirjutas:<br> +> > > And what about security issues and bugs to those backports? It will use<br> +> > > more packager ressource to patch backports than to provide newer<br> +> > > versions, won't it?<br> +> ><br> +> > If there is security issue then you have to fix it on cauldron too (usually<br> +> > with new version, so you can backport it to stable version). At least<br> +> > before release. And after backports are closed you can upgrade to latest<br> +> > stable version (for example mga3) and get patched version this way. I<br> +> > don't see the problem here.<br> +> ><br> +><br> +> So you mean that backports are supported for 9 months and then you have to<br> +> upgrade to the next Mageia if you want security fixes... That's not what I call<br> +> support :/ What about people who want not to upgrade their whole system to the<br> +> next Mageia and still get support for that backport they installed?<br> +I don't think that we need to support backports that much. It should be clear that backports might not get all security updates. We should guarantee that it's possible to upgrade to next stable release and that's about it. We really don't have resources for more.<br> + +And if user doesn't want to upgrade to next release but at the same time wants security updates s/he can always downgrade.</p> +<p>--<br> +Sander<br> +</p> -- cgit v1.2.1