Additions:
The workflow may have evolved a bit :)
See what is done on fedora project:
~- http://fedoraproject.org/wiki/ReleaseEngineering/Overview
~- http://sexysexypenguins.com/2011/09/19/building-an-os-the-workflow/
See what is done on fedora project:
~- http://fedoraproject.org/wiki/ReleaseEngineering/Overview
~- http://sexysexypenguins.com/2011/09/19/building-an-os-the-workflow/
Additions:
ToDo:
~- add communication and marketing team interactions (same team at the moment), internal (blog+wiki) + external comm'
~- qa (testers) and bugsquad (triage) should interact too
~- perhaps have community management be interaction of competences
~- add sysadm and webteam for infrastructure
~- translator work on packages (descriptions) and software too (working with upstream)
~- add communication and marketing team interactions (same team at the moment), internal (blog+wiki) + external comm'
~- qa (testers) and bugsquad (triage) should interact too
~- perhaps have community management be interaction of competences
~- add sysadm and webteam for infrastructure
~- translator work on packages (descriptions) and software too (working with upstream)
Additions:
===add a zoom on build-system===
the whole way we import rpm is quite obscure
ie, where to check what is missing, what is actually done, etc
what is needed to be done, what is the planning
http://pkgsubmit.mageia.org/
who is in charge of signing pkgs ?
the whole way we import rpm is quite obscure
ie, where to check what is missing, what is actually done, etc
what is needed to be done, what is the planning
http://pkgsubmit.mageia.org/
who is in charge of signing pkgs ?
Additions:
ToDo: add MageiaReleaseCycle description (backports / updates on current version)
