summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/attachments/20110616/acf83a0c/attachment.html
blob: a5d0c2f772f52b3ce4883fe710838486d1925c1c (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
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
    <title></title>
  </head>
  <body text="#000000" bgcolor="#ffffff">
    by <strong><a
href="https://forums.mageia.org/en/memberlist.php?mode=viewprofile&amp;u=359">pmithrandir</a></strong>
    &raquo; Jun 13th, '11, 20:21
    <div class="content">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.</div>
  </body>
</html>