Mageia 2 (Calendar, support and details)

After some time (and intense discussions in the community of Mageia), already know through Anne Nicholas how will the release and support cycle of Mageia 2:

Development schedule for Mageia 2.

  • Alpha 1: 16/11/2011
  • Alpha 2: 14/12/2011
  • Beta 1: 20/01/2012
  • Versions freeze: 06/02/2012
  • Artwork freeze: 10/02/2012
  • i18n freeze: 10/02/2012
  • Beta 2: 14/02/2012
  • Releases freeze: 06/03/2012
  • RC: 09/03/2012
  • Final Release: 04/04/2012

This means that basically, it will be the same as the one used for Mageia 1.

Actually (and as a curiosity) there were 3 proposals for cycles:

1 Proposal:
New version every 6 months -> maximum life of each cycle of 12 months
(Fedora, Ubuntu, Mandriva <2010.1 && Mandriva ! = 2006.0)

Proposal 2 (and which was decided would be the one used):
New version every 9 months -> maximum life of each cycle of 18 months
(~ opensuse and the one used for Mageia 1)

3 Proposal:
New version every 12 months -> maximum life of each cycle of 24 months
(Mandriva > 2010.1)

If you notice, using proposal # 2 you are not completely synchronized with the launches of Gnome y KDE, However Nicolas (former Director of Engineering at Mandriva) says he supported this proposal based on his previous experience with Mandriva, we'll see how it goes 🙂

 A little more technical aspects were also discussed, such as allowing the user to go backwards in each step of the installation (a button Back, as there is one of Next well put one of Back), as well as an option that allows the user to install all kinds of proprietary codecs together with the system. Another aspect / idea that was debated is whether they should make a 64bit LiveCD or not.

Personally, the fact that there is no Back anywhere in the installation process, I see it as something really retrograde and absurd. Keep in mind that if I put any data wrong, I can only correct it by restarting the computer and starting the whole process again, this idea was discussed before in Mandriva and now it is still debated in Mageia, I sincerely hope they just put it into practice ...

But this is not all. At the point «desk» Mageia 2 will KDE 4.7 as well as with Gnome 3.2 and they are talking if they should change the theme IaOra. One suggestion could be taken seriously: «more games - of any kind, just more games«It may seem funny to us but it has already started to be discussed 😉. We will also have new themes KDM / GDM same as with new icons.

On the system itself we will have Linux v3.0, GCC v4.6, python v3, and RPM 4.9, the inclusion of systemd.


Leave a Comment

Your email address will not be published. Required fields are marked with *

*

*

  1. Responsible for the data: Miguel Ángel Gatón
  2. Purpose of the data: Control SPAM, comment management.
  3. Legitimation: Your consent
  4. Communication of the data: The data will not be communicated to third parties except by legal obligation.
  5. Data storage: Database hosted by Occentus Networks (EU)
  6. Rights: At any time you can limit, recover and delete your information.

  1.   hypersayan_x said

    They can release 3-month or 3-year versions if they want, but personally I think the cyclic release model is decadent for desktop computers, the best would have been to use a rolling release model like the one Arch is based on, which has proven to be quite stable despite being constantly updated, we also have the case of Chakra, PCLOS or LMDE have shown that a really friendly distro rolling release can be made.
    My first distro was Mandriva, but the direction Mandriva / Mageia is taking I don't like at all, one that comes with a lot of interesting news, I admit it, but it seems that it doesn't come out anymore, and the other one remains in the past.

    PS: Ouch, with this I have gained a few mandrillian enemies 😛

    1.    Courage said

      I partly agree with you. I consider it a good idea to take out a Current rolling branch and another Stable cycling for companies, since something rolling is not a good idea in companies (I don't quite understand why but I imagine that it is in case some package is not mature it sends everything to the horn )

      Frugalware works like this