Wiki source for Blog20110124AnISOalphaForWhat


Show raw source

Well to give minimal context : rebuilding is in progress, build-system is being widely tested by packagers

===Building an ISO alpha for Mageia: which objectives?===
~- to be usable: hmmm not yet, hence alpha, which mean, testing, not expecting to working without having followed what is needed to make it work (hmm reminds me of KDE4 /o\)
~- to be tested: yep, once you apply and follow all that's needed and identify what is still missing
~- to contribute: yep
~- to initiate testings: of course
~- on a wider view:
~~- test processes: upload, communication, mirrors, documentation, support
~~- first release: as in "release early, release often" or in "barely usable" unless you know what you're expecting
~- so, what are you expecting?
~~- working upgrade from 2010.1 & 2010.2? hmm not yet, submit bugs please :)
~~- install in a VM for minimal impacts, yeah should work, with some workarounds to apply imho
~~- urpmi task-kde4 task-gnome task-xfce # yeah
~~- install a working chroot or VM to contribute building package for Mageia

===What are next steps===
prerequisites:
~- documentation (wiki?)
~- announcement
~- mirrors / downloads
~- reporting bugs (bugzilla) / support (forum)
~- official website
~-

not to be confused with the alpha
~- bootstrap,
~- boot.iso,
~- boot network,
~- distro limitée sur iso,
~- test dans des vm de virtualbox

jusque là, rien de nouveau "nothing new at the west?"
~- urpmi task-minimal-gnome et ça marche
~- 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 infrastructure
~- 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 ?
~-


Valid XHTML :: Valid CSS: :: Powered by WikkaWiki