From Mageia wiki
This page is dedicated to **Mageia post-mortem**. It should help us to improve process for Mageia 2
Contents
Brainstorming
What we should keep
What went wrong or should be improved
- string freeze missing
- version freeze must be stricter
- release freeze must be stricter
- iso-builders must scale
- qa of final isos too short, should be at least 10 days
- Maybe remind any new qa testers how to rsync each set of new isos: dvgevers didn't realise one can write the new set over the old one and save a huge number of bits downloaded and time until very late in the sequence of isos produced :((
- websites should be done at least ~7 days before in english, so it can be proofread, fixed (~2 days), and then translated (~4 days), and available in time for release.
- number of qa-testers too low for pre-release testing (also alpha, beta, ...)
- perhaps a bit more time allocated to bugfixing between pre-release and freeze
- should there be an artwork freeze?
- Very difficult for new packagers to participate (all the mentors seems to require quite a lot of packaging experience from "new" packagers)
Result of post-mortem
Here are the big topics we will have to focus on
Improve freeze planning
- i18n: add string freeze
- follow freeze planning more carefully
- add artwork integration freeze
Improve isos build process
- backups for isos builders
- automatic builds for isos
How to make people test, report and get bugs fixed in time
- more time allocated to bugfixing between pre-release and freeze: pb is bugs are always fixed in last minute. Same pb for tests
- qa of final isos too short, should be at least 10 days: having automatic builds to check in a more frequent way, organize testers in a better way ; improve documentation and training
- number of qa-testers too low for pre-release testing (also alpha, beta, …)
Mentoring
- Very difficult for new packagers to participate (all the mentors seems to require quite a lot of packaging experience from “new” packagers): we do need minimal requirements to keep good quality level but we need also to improve that process and the way it's managed on daily base.
See discussions on that post-mortem: Post-mortem review