summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/attachments/20120206/47dc96a9/attachment.html
diff options
context:
space:
mode:
Diffstat (limited to 'zarb-ml/mageia-dev/attachments/20120206/47dc96a9/attachment.html')
-rw-r--r--zarb-ml/mageia-dev/attachments/20120206/47dc96a9/attachment.html34
1 files changed, 34 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/attachments/20120206/47dc96a9/attachment.html b/zarb-ml/mageia-dev/attachments/20120206/47dc96a9/attachment.html
new file mode 100644
index 000000000..72431bc2a
--- /dev/null
+++ b/zarb-ml/mageia-dev/attachments/20120206/47dc96a9/attachment.html
@@ -0,0 +1,34 @@
+<p>And, don&#39;t forget, we still have a package named firefox-beta. If we stick with FF10, then some day we will come to a situation of firefox-10.0.4 and firefox-beta-15b1 for Mageia 2, which is unacceptable. Or, we should make an exception on firefox-beta, it should be obsoleted by updated firefox for stable distros.</p>
+
+<div class="gmail_quote">在 2012-2-6 下午3:27,&quot;Funda Wang&quot; &lt;<a href="mailto:fundawang@gmail.com">fundawang@gmail.com</a>&gt;写道:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
+<p>The key is, we always have the latest series of supported product line from upstream, neither latest version nor latest supported version.</p>
+<p>And, such an update policy is based on the imagination of 70% of Mageia 2 users will upgrade to Mageia 3 immediately when released.</p>
+<div class="gmail_quote">在 2012-2-6 上午10:07,&quot;Funda Wang&quot; &lt;<a href="mailto:fundawang@gmail.com" target="_blank">fundawang@gmail.com</a>&gt;写道:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
+
+<p>I would suggest another support policy.</p>
+<p>* For cauldron, we always have latest versions of firefox and thunderbird, no matter whether it is ESR.</p>
+<p>* For released distros, we always update it till next ESR. i.e., for Mageia 1, we will have FF 9.0.1, 10.0, 10.0.1, 10.0.2, 10.0.3, but not 11.0. If time passed, we will go directly 10.0.x to 17.0 ESR.</p>
+<p>* For xulrunner, we always use latest ESR version for cauldron and released distros.</p>
+<div class="gmail_quote">在 2012-1-13 上午9:20,&quot;Maarten Vanraes&quot; &lt;<a href="mailto:alien@rmail.be" target="_blank">alien@rmail.be</a>&gt;写道:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
+
+
+see <a href="https://blog.mozilla.com/blog/2012/01/10/delivering-a-mozilla-firefox-extended-support-release/" target="_blank">https://blog.mozilla.com/blog/2012/01/10/delivering-a-mozilla-firefox-<br>
+extended-support-release/</a><br>
+see <a href="https://wiki.mozilla.org/images/9/9d/Esr-release-overview.png" target="_blank">https://wiki.mozilla.org/images/9/9d/Esr-release-overview.png</a><br>
+<br>
+ESR is a 1y extended supported release...<br>
+<br>
+looking at the image we&#39;d be having supported versions for our 9month release<br>
+schedule every time... we should totally use this release and not go towards<br>
+FF11 for our release.<br>
+<br>
+We&#39;ve been complaining about the too quick release schedule... this is our<br>
+chance!<br>
+<br>
+( i think if the FF maintainer wishes, he could also do backports of the<br>
+regular releases... )<br>
+<br>
+i&#39;m hoping everyone agrees? including FF maintainer?<br>
+</blockquote></div>
+</blockquote></div>
+</blockquote></div>