1 files changed, 44 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/attachments/20110613/4f2f9de9/attachment-0001.html b/zarb-ml/mageia-dev/attachments/20110613/4f2f9de9/attachment-0001.html
new file mode 100644
index 000000000..0add9d432
--- /dev/null
+++ b/zarb-ml/mageia-dev/attachments/20110613/4f2f9de9/attachment-0001.html
@@ -0,0 +1,44 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html>
+  <head>
+    <meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
+  </head>
+  <body text="#000000" bgcolor="#ffffff">
+    From <strong><a
+href="https://forums.mageia.org/en/memberlist.php?mode=viewprofile&amp;u=359">pmithrandir</a></strong> 
+    on the forum<br>
+    <br>
+    On my side, I think mageia should do a "mix" of others idea.<br>
+    <br>
+    I would say : <br>
+    - A release every year.<br>
+    - During this year, a way to update some popular stuff (firefox,
+    chrome, libreoffice...)<br>
+    - During this year also a way to add some new package if needed or
+    if there is some instant success for a new software.<br>
+    <br>
+    Every 3 years, the release is LTS and that mean it would be maintain
+    for 4 years.<br>
+    <br>
+    So at the same time, mageia would be in 3 mode : <br>
+    - The LTS<br>
+    - The common release<br>
+    - The cauldron.<br>
+    <br>
+    With that kind of stuff, you should have no more than one release
+    for public at a time, and just one LTS.<br>
+    If you update main software(we could define a list of no more than
+    20 software) people who are crasy about new function, or developper
+    who need tham to develop new stuff would be happy.<br>
+    <br>
+    BTW : I think mailing list are totally outdated and that mageia
+    should have a special section in this forum for these discussion, or
+    maybe another forum.<br>
+    It's totally impossible for people who want to participate sometimes
+    to follow you emails everydays. It's much faster to read some topic
+    on a forum than dozens emails. And your final user should be able to
+    know what happen easily. It would be a big + in front of others
+    distributions.<br>
+    <br>
+  </body>
+</html>