summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/attachments/20110616/50b25b5c/attachment-0001.html
blob: a01c34e2383f1e8e29e78105f97da77019ba9904 (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
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body text="#000000" bgcolor="#ffffff">
    Le 16/06/2011 19:57, lebarhon a &eacute;crit&nbsp;:
    <blockquote cite="mid:4DFA4420.5090709@free.fr" type="cite">
      <meta content="text/html; charset=ISO-8859-1"
        http-equiv="Content-Type">
      &nbsp;by <strong><a moz-do-not-send="true"
href="https://forums.mageia.org/en/memberlist.php?mode=viewprofile&amp;u=359">pmithrandir</a></strong>
      &raquo; Jun 13th, '11, 20:21
      <blockquote cite="mid:4DFA43A9.1080003@free.fr" type="cite">
        <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>
      </blockquote>
      by <strong><a moz-do-not-send="true"
href="https://forums.mageia.org/en/memberlist.php?mode=viewprofile&amp;u=448">claire</a></strong>
      &raquo; Jun 16th, '11, 14:27
      <div class="content">
        <blockquote>
          <div><cite>pmithrandir wrote:</cite>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>
          </div>
        </blockquote>
        <br>
        <br>
        I completely agree with this. There is no real need to rush
        releases as long as new versions are easily available. I know
        backports repo is available but its not very user friendly. As
        an example, the newer versions of Openshot video editor have a
        very nice feature of being able to do animated titles. To be
        able to use them you need Blender 2.5. Whilst Mageia includes
        Openshot 1.3.1 (which errors with missing plugins btw) which at
        time of writing is current it still has Blender 2.49b.<br>
        <br>
        It would be useful if there were a nice user friendly way to
        upgrade Blender when it is backported. Something to let ordinary
        users know a newer version is available and a simple click to
        upgrade it.<br>
        <br>
        LTS releases in Ubuntu IMHO are a great idea and one which would
        add value to mageia as a potential server/business OS where
        stability over time is crucial.<br>
        <br>
        I dont think Joe Bloggs really cares about a 6 monthly
        distribution upgrade, only that new versions of the software
        they use are easily obtainable in the mean time and won't break
        the distribution upgrade when it comes around.</div>
    </blockquote>
    by <strong><a
href="https://forums.mageia.org/en/memberlist.php?mode=viewprofile&amp;u=468">roadrunner</a></strong>
    &raquo; Jun 16th, '11, 15:35
    <div class="content">
      <blockquote>
        <div><cite>claire wrote:</cite>
          <blockquote>
            <div><cite>pmithrandir wrote:</cite>I dont think Joe Bloggs
              really cares about a 6 monthly distribution upgrade, only
              that new versions of the software they use are easily
              obtainable in the mean time and won't break the
              distribution upgrade when it comes around.</div>
          </blockquote>
        </div>
      </blockquote>
      Speaking as a typical "Joe Bloggs", all I'm interested in is
      keeping my applications up to date with the occasional
      distribution upgrade. I'm not interested in regular release cycles
      because I feel that this leads to "rush-jobs", which in turn,
      leads to bugs galore. I'm more interested in a solid reliable
      distribution upgrade on the "it'll be ready when it's ready"
      basis.<br>
      <br>
      .\\artin</div>
    <div id="sig3679" class="signature"><span style="font-style:
        italic;">- Mageia 1 32-bit - KDE SC 4.6.3 -<br>
        - AMD Athlon 64 X2 5000+ CPU -<br>
        - 4Gb RAM - nVidia 8500GT GPU -</span></div>
  </body>
</html>