As said in a previous post, people are now back to work, focused on Mageia 3 release. So it was time again to define the specifications for the coming release. We then thought it was time to improve the process used for Mageia 2:
- the list of submitted specifications was very long and we only implemented a few of them,
- lots of submitted ideas were just undefined or were missing a lot of information,
- some submitted specifications were not really specifications like “update to xxx version” for minor packages,
- we got some kind of catalog of items without logic,
- and many of them were proposed without any resources.
Mageia has now its own Features policy. It defines what is a feature, how it can be proposed, and what criteria are used to choose the official one for coming releases.
The process is the following:
- make proposals for Mageia 3 after reading the policy. People had to use a template to formalize it,
- all the proposals were then read and sorted. All the contributers were asked to complete it if necessary or discuss it on mageia-dev mailing-list,
- final choice was made.
We finally proposed a list divided into 4 kinds of features:
- Accepted features: now fully described and will be followed in teams meeting,
- Pending features: may be implemented but for now we miss resources information,
- Features to be detailed: need to be completed,
- Refused features: refused for various reasons: discussions already in progress, duplicated features, …
Let see now first results of the implementation of these features in first alpha release planned for 4th of september!