summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/attachments/20120527/3ce93a66/attachment.html
blob: 55a80eb8c50917b6b1ec9c4804ecc501074ab84c (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
<p>Le 27 mai 2012 04:33, &quot;Franklin Weng&quot; &lt;<a href="mailto:franklin@goodhorse.idv.tw">franklin@goodhorse.idv.tw</a>&gt; a écrit :<br>
[...]</p>
<p>&gt;   Now my question is that, will the KDE update policy in<br>
&gt; backports be still the same as before?<br>
&gt;<br>
&gt; I remember that when discussing if Mageia 1 would have KDE 4.7 in<br>
&gt; backports, the answer was no because that kdepim was too unstable.</p>
<p>It was part of the problem &amp; used to show that it was not that easy to do it.</p>
<p>[...]</p>
<p>&gt; For Mageia 2, again I&#39;d like to ask, if we will have KDE 4.9 in<br>
&gt; backports after it releases in August?<br>
&gt;<br>
&gt; (Yes, I know that I can upgrade my KDE using cauldron.  But no, I<br>
&gt; don&#39;t consider to upgrade my box with cauldron... it is far too<br>
&gt; unstable than any version of kdepim.)</p>
<p>So here we&#39;ve got some problems:<br>
- Backports are not functional.<br>
- Kde is still too big for a backport especially regarding our current (draft) backport policy where it should be validated by our QA. Not to mention that we&#39;ll have to update/backport somes dependencies to allow this.<br>

- I personally won&#39;t push it to backport.</p>
<p>Regards,<br>
</p>