summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/attachments/20120608/7e8c5812/attachment.html
blob: 8b6981e389a5d9ede41a4d896a02383522ae93f5 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
<p>On Jun 8, 2012 2:33 PM, &quot;Samuel Verschelde&quot; &lt;<a href="mailto:stormi@laposte.net">stormi@laposte.net</a>&gt; wrote:<br>
&gt;<br>
&gt; Le vendredi 8 juin 2012 11:40:59, Sander Lepik a écrit :<br>
&gt; &gt; 08.06.2012 11:51, Samuel Verschelde kirjutas:<br>
&gt; &gt; &gt; And what about security issues and bugs to those backports? It will use<br>
&gt; &gt; &gt; more packager ressource to patch backports than to provide newer<br>
&gt; &gt; &gt; versions, won&#39;t it?<br>
&gt; &gt;<br>
&gt; &gt; If there is security issue then you have to fix it on cauldron too (usually<br>
&gt; &gt; with new version, so you can backport it to stable version). At least<br>
&gt; &gt; before release. And after backports are closed you can upgrade to latest<br>
&gt; &gt; stable version (for example mga3) and get patched version this way. I<br>
&gt; &gt; don&#39;t see the problem here.<br>
&gt; &gt;<br>
&gt;<br>
&gt; So you mean that backports are supported for 9 months and then you have to<br>
&gt; upgrade to the next Mageia if you want security fixes... That&#39;s not what I call<br>
&gt; support :/ What about people who want not to upgrade their whole system to the<br>
&gt; next Mageia and still get support for that backport they installed?<br>
I don&#39;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&#39;s possible to upgrade to next stable release and that&#39;s about it. We really don&#39;t have resources for more.<br>

And if user doesn&#39;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>