Additions:
~- define what is to be tested: mainly the infrastructure
Deletions:
Additions:
~~- urpmi task-kde4 task-gnome task-xfce # yeah
~~- install a working chroot or VM to contribute building package for Mageia
not to be confused with the alpha
jusque là, rien de nouveau "nothing new at the west?"
~- or urpmi task-kde4
tadaaa and it works ?
What pre-requisites for an alpha? When is it worth it, what makes it worth?
~- working boot
~- basic artwork (not the whole possibilities), provide doc' to add some ;-) (involve artwork and marketing teams)
~- define what is to be tested: mainly the infrastracture
~- define the audience and what is to be done "later" for example
~~- external communication is for later
~~- currently validate documentations, publish objectives of each version and their form, rework roadmap for infrastructure (bugzilla, forums, wiki... in which order?)
~~- currently use existing infrastructure and build upon it to identify requirements to be added
~~- identify MUST requirements to be addressed (following MoSCoW methodology)
~- package tree published? signed? api.mageia.org/mirror.xml ?
~- later : http://smolts.org http://hardware4linux.org hcl.mageia.org ?
~~- install a working chroot or VM to contribute building package for Mageia
not to be confused with the alpha
jusque là, rien de nouveau "nothing new at the west?"
~- or urpmi task-kde4
tadaaa and it works ?
What pre-requisites for an alpha? When is it worth it, what makes it worth?
~- working boot
~- basic artwork (not the whole possibilities), provide doc' to add some ;-) (involve artwork and marketing teams)
~- define what is to be tested: mainly the infrastracture
~- define the audience and what is to be done "later" for example
~~- external communication is for later
~~- currently validate documentations, publish objectives of each version and their form, rework roadmap for infrastructure (bugzilla, forums, wiki... in which order?)
~~- currently use existing infrastructure and build upon it to identify requirements to be added
~~- identify MUST requirements to be addressed (following MoSCoW methodology)
~- package tree published? signed? api.mageia.org/mirror.xml ?
~- later : http://smolts.org http://hardware4linux.org hcl.mageia.org ?
Deletions:
~~-
à ne pas confondre avec une alpha
jusque là, rien de nouveau,
~- ou urpmi task-kde4
et ça marche ?
quand vaut-il sortir une alpha ?
Additions:
à ne pas confondre avec une alpha
~- bootstrap,
~- boot.iso,
~- boot network,
~- distro limitée sur iso,
~- test dans des vm de virtualbox
jusque là, rien de nouveau,
~- urpmi task-minimal-gnome et ça marche
~- ou urpmi task-kde4
et ça marche ?
quand vaut-il sortir une alpha ?
~- bootstrap,
~- boot.iso,
~- boot network,
~- distro limitée sur iso,
~- test dans des vm de virtualbox
jusque là, rien de nouveau,
~- urpmi task-minimal-gnome et ça marche
~- ou urpmi task-kde4
et ça marche ?
quand vaut-il sortir une alpha ?