On Fri, 2005-09-23 at 11:32 +1000, Phillip Berry wrote: > Hello, > > Could some point me to, or provide a more specific breakdown of some of the > roles and tasks that would need to be tended to? > > Forgive me if i appear ignorant to the problems and issues with maintaining > an > enterprise ready tree but in my mind running a stable tree would involve : > > 1. Identifiying a version of a package that is stable keep upgrades to a reasonable minimum ... "never touch a running system" > 2. Marking that package as stable that includes lots of testing. Then some more testing. ... Also each major release (2005.0/2005.1/2006.0/...) would most likely be its own branch and need testing ... Did I mention QA and testing? ;-) > 3. Pushing that package to the rsync servers Why rsync? updates for an "enterprise" tree should be infrequent enough for tarballs to be easier (less overhead, easier to see what needs to be fetced, ...) > 4. ? Backport security fixes to older versions? > 5. ? > 6. ? > > What are the items that are missing from my list? That would only provide a stable ebuild base. Extra items such as reliable support etc. aren't even mentioned here but would most likely be needed / very useful.
Patrick -- Stand still, and let the rest of the universe move
signature.asc
Description: This is a digitally signed message part
