Mageia 2 Release Details Revealed
After an extensive discussion with the community on the Mageia developmental mailing list, Anne Nicolas revealed the results concerning Mageia release and support cycles as well as the release schedule for Mageia 2. The consensus was to use basically the same cycle used in Mageia 1.
Three proposals where given for discussion:
Proposal 1:
6 months release cycle -> 12 months life cycle
( Fedora, Ubuntu, Mandriva < 2010.1 && Mandriva != 2006.0 )Proposal 2:
9 months release cycle -> 18 months life cycle
( ~ opensuse and the one we used for Mageia 1 )Proposal 3:
12 months release cycle -> 24 months life cycle
( Mandriva > 2010.1 )
Since there are pros and cons to each, a lengthy discussion followed. Nicolas, former Director of Engineering with Mandriva, favored Proposal 2 based on her experience with Mandriva. The pros of Proposal 2 include releasing in-between other popular distribution's releases in order to stand out and not be lost in the news behind others such as openSUSE, Ubuntu, or Fedora. This tends to be a disadvantage as well since it is not in sync with GNOME or KDE releases and sometimes falls on or near holidays.
Proposal 1 can offer better hardware support and more up-to-date software, but the tight schedule can lead to more stress and pressure and possibly result in less quality assurance. While Proposal 3 allows users longer between upgrades, it can also make these upgrade more risky due to bigger changes. It also can cause hardware support lag. Probably the worse disadvantage for a new project is more time between being in the spotlight.
So, Proposal 2 was chosen. The developmental cycle will be nine months and each release will be supported for 18. In addition, the new release schedule was posted. Development has already begun and an initial alpha will be released November 16. The Final Release will come on April 4, 2012.
The full schedule is:
● 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
Some of the technical aspects being discussed include an easier installation. Developers wonder if some additional screens and choices can be hidden from users while giving users a choice about non-free and tainted media. Another idea is to finally give users a "Back" button during the install. A long time complaint with Mandriva, and now Mageia, is that if a user clicks "Next" and changes their mind about something, the only way back is to reboot and start all over. This will be a most welcome addition. Another long awaited option being considered is a 64-bit LiveCD.
The system itself will likely feature Linux 3.0, GCC 4.6, Python 3, and RPM 4.9. systemd is also being discussed. Many distributions are switching to systemd, so the prospect is not so radical anymore as the kinks are being ironed out. Another bold idea is to replace the current synthesis package metadata handling to an XML-based solution. Some think this will bring a speed increase.
In the area of desktop environments, it appears Mageia 2 will feature KDE 4.7 and GNOME 3.2. There is also talk of replacing the attractive IaOra theme with an Oxygen-like theme. Let's hope it's from scratch and doesn't come with the NVIDIA conflicts found in Oxygen currently. "More games - any kind of games, just more of them" is a fun idea being discussed. New Kdm/Gdm screens, new icons, and codenames are also on the table.
As an aside, our old friend Beranger is currently providing third party applications for Mageia 1. Interestingly, he seems to think Linux 3.0 is a big mistake for Mageia.
Susan Linton is a Linux writer and the owner of tuxmachines.org.
Realizing the promise of Apache® Hadoop® requires the effective deployment of compute, memory, storage and networking to achieve optimal results. With its flexibility and multitude of options, it is easy to over or under provision the server infrastructure, resulting in poor performance and high TCO. Join us for an in depth, technical discussion with industry experts from leading Hadoop and server companies who will provide insights into the key considerations for designing and deploying an optimal Hadoop cluster.
Sponsored by AMD
Built-in forensics, incident response, and security with Red Hat Enterprise Linux 6
Every security policy provides guidance and requirements for ensuring adequate protection of information and data, as well as high-level technical and administrative security requirements for a system in a given environment. Traditionally, providing security for a system focuses on the confidentiality of the information on it. However, protecting the data integrity and system and data availability is just as important. For example, when processing United States intelligence information, there are three attributes that require protection: confidentiality, integrity, and availability.
Learn more about catching the bad guy in this free white paper.
Sponsored by DLT Solutions
| Designing Electronics with Linux | May 22, 2013 |
| Dynamic DNS—an Object Lesson in Problem Solving | May 21, 2013 |
| Using Salt Stack and Vagrant for Drupal Development | May 20, 2013 |
| Making Linux and Android Get Along (It's Not as Hard as It Sounds) | May 16, 2013 |
| Drupal Is a Framework: Why Everyone Needs to Understand This | May 15, 2013 |
| Home, My Backup Data Center | May 13, 2013 |
- Designing Electronics with Linux
- New Products
- Making Linux and Android Get Along (It's Not as Hard as It Sounds)
- Dynamic DNS—an Object Lesson in Problem Solving
- Using Salt Stack and Vagrant for Drupal Development
- Validate an E-Mail Address with PHP, the Right Way
- Why Python?
- Linux Systems Administrator
- Tech Tip: Really Simple HTTP Server with Python
- Build a Skype Server for Your Home Phone System
- Dynamic DNS
31 min 40 sec ago - Reply to comment | Linux Journal
1 hour 30 min ago - Reply to comment | Linux Journal
2 hours 20 min ago - Not free anymore
6 hours 22 min ago - Great
10 hours 9 min ago - Reply to comment | Linux Journal
10 hours 17 min ago - Understanding the Linux Kernel
12 hours 32 min ago - General
15 hours 1 min ago - Kernel Problem
1 day 1 hour ago - BASH script to log IPs on public web server
1 day 5 hours ago
Enter to Win an Adafruit Pi Cobbler Breakout Kit for Raspberry Pi

It's Raspberry Pi month at Linux Journal. Each week in May, Adafruit will be giving away a Pi-related prize to a lucky, randomly drawn LJ reader. Winners will be announced weekly.
Fill out the fields below to enter to win this week's prize-- a Pi Cobbler Breakout Kit for Raspberry Pi.
Congratulations to our winners so far:
- 5-8-13, Pi Starter Pack: Jack Davis
- 5-15-13, Pi Model B 512MB RAM: Patrick Dunn
- 5-21-13, Prototyping Pi Plate Kit: Philip Kirby
- Next winner announced on 5-27-13!
Featured Jobs
| Linux Systems Administrator | Houston and Austin, Texas | Host Gator |
| Senior Perl Developer | Austin, Texas | Host Gator |
| Technical Support Rep | Houston and Austin, Texas | Host Gator |
| UX Designer | Austin, Texas | Host Gator |
| Web & UI Developer (JavaScript & j Query) | Austin, Texas | Host Gator |
Free Webinar: Hadoop
How to Build an Optimal Hadoop Cluster to Store and Maintain Unlimited Amounts of Data Using Microservers
Realizing the promise of Apache® Hadoop® requires the effective deployment of compute, memory, storage and networking to achieve optimal results. With its flexibility and multitude of options, it is easy to over or under provision the server infrastructure, resulting in poor performance and high TCO. Join us for an in depth, technical discussion with industry experts from leading Hadoop and server companies who will provide insights into the key considerations for designing and deploying an optimal Hadoop cluster.
Some of key questions to be discussed are:
- What is the “typical” Hadoop cluster and what should be installed on the different machine types?
- Why should you consider the typical workload patterns when making your hardware decisions?
- Are all microservers created equal for Hadoop deployments?
- How do I plan for expansion if I require more compute, memory, storage or networking?



Comments
I do not understand it
I do not understand it either. Seems somewhat superfluous.
a commendable project
This is a worthy project - It looks like the Mageia community really have their act together and I applaud them. I'm glad Mandriva was forked.
Information
Thank for your information
WoW
Wow,
What a completely useless article.
C'mon, LJ. Really!
--KK
beranger
He's not only packaging software for mageia but he is using KDE4! And he is even submiting bug reports!
um?
Begging your pardon, I read this article twice and I still don't know what Mageia *is*.
Yup. Same thing here!
Yup. Same thing here!
me too, but then ...
it gives one another opportunity to contribute to Google's search statistics ;-)
"Mageia is a fork of Mandriva Linux, supported by a not-for-profit organisation of recognized and elected contributors" -- http://mageia.org/
Don't make another Ubuntu.
Don't make another Ubuntu.
Thanks for mentioning, but it needs a correction
For Mageia Cauldron (cooker), not for Mageia 1!
(Cauldron has already some major updates in terms of KDE4, GNOME3 and the corresponding libs.)