From Mageia wiki
Jump to: navigation, search


Goal(s)

  • test drive Mageia build system.
  • better understand how we all can collaborate through teams and the council.

Of course, we expect this to be a very first version but stable enough to be used by a large audience.

Code name

Cantine


Expected milestones

Check Stage Expected date Actual Public Step description Off by
OK setup Dec '10 Nov-Jan '11 packagers repositories/packaging/build system complete and ready for working 1 month
OK initial Dec '10 Dec-Jan packagers import and cleanup of repositories 1 month
OK bootstrapping Dec '10 Feb packagers building Mageia on itself 1 month
OK alpha 1 release Dec '10, then Jan '11 February, 14th + testers & developers first ISO release (aka "ISO 0"), technical preview 1 month
OK alpha 2 release March, 15th March, 15th //same// more cleanups, theme improvements on time!
OK beta 1 release April, 5th + test users on time!
OK pkg version freeze April, 20th   on time!
OK beta 2 release April, 26th + reviewers on time!
OK i18n freeze May, 13th  All translations integrated (checklist to do) on time!
::: design ::: ::: ::: :::  All final artwork integrated, everything finalized (checklist to do) :::
::: release ::: ::: ::: ::: :::
OK RC release May, 18th on time!
=> finale release June, 1st everyone Mageia 1: first stable release (aka "ISO 1") on time!

At this stage, DO NOT EXPECT any alpha ISO release to be a "general audience-ready" system.

Alpha ISO main and first goal is to test drive the whole build system and the project's organization.

Features

(see http://en.wikipedia.org/wiki/MoSCoW_Method for the MUST/SHOULD/COULD/WILL NOT priorities)

MUST HAVE

  • alpha 1 => Be clear of reference or licensing issue related to Mandriva
    • task: cleanup, packagers
    • theme and icons, documentation
    • /etc/release
    • licensing issue; specifically about pieces of software without an explicit license
    • specific Mandriva packages to check
    • Remove:
      • documentation (not cleared from MDV)
      • existing themes and icons must be replaced if not explicitly freely licensed
      • script/automate all this (importing, removing, checking)
    • Replace:
      • themes and icons => (artwork team) design new theme, new default icons for action/app/media/? and new icons for all system
  • (buildsystem) => **Rebuilt packages with Mageia tags
  • alpha 1 => TODO (buildsystem) New packages signatures
  • alpha 2 => PENDING (artwork, packagers) Mageia brand and logo; on:
    • boot screen
    • background
    • tools
    • Careful, design/improve/follow guidelines in this regard.
    • complete available packages
  • **all** => TODO (marcom) **be appropriately marketed for what it is** (see the "DO NOT EXPECT" line)

SHOULD HAVE

  • **alpha 1** => PENDING (misc, nanar) **Updates mirrors policy**
  • **finale** => TODO (marcom) **be released with clear project means and goals**

COULD HAVE

  • beta => Automated build/test basic cycle for ISO
  • finale => An "approved/stable for all audiences" label

WILL NOT HAVE

  • A new release cycle: time-based release for the moment, with alpha/beta/rc classical cycle
  • Work related to rolling/backport topic: do not hesitate to involve early in order to make it possible though :-)
  • Specific development: infrastructure is in progress, community is building (organizationnal part of the project), so indeed few new development may be available in the distribution, have a look at http://mageia-app-db.tuxette.fr/projects/mageia-app-db/wiki
  • New features: usual versions of classical software are available, like latest stable kernel, LibreOffice, GNOME 3, KDE 4.6 see release notes for details

(these items may be taken into consideration for the next run of Mageia 2)