Hi all,

As part of the new governance procedure we are also clarifying what the
release process looks like.  One thing we have come up with is the
notion of a "release team".  Broadly, this is the set of all committers
who have new code in a given release.  The implication is that these
people should be available during the release process to help fix bugs
and do QA.

Does this mean that everyone else gets to sit back and watch?  Of
course not; it's just a quick little list of those people who have done
measurable new work leading up to a release.  And maybe a little
leverage the release manager can use to try and encourage (guilt)
committers into helping with the QA process.

There are more clarifications to come as we finish up the Chicago
discussions.  But I thought I would start this early, and I put a
little script in /docs/scripts/release to help future RMs too.  So,
without further discussion, here is the release team for 1.2:

 ruben.perez ,  mmoorman ,  akm220 ,  nejc ,  matjaz ,  twunden ,
 msutton ,  Nejc ,  jholtzman ,  rrolf ,  denmeyer ,  mketterl ,
 greg_logan ,

Many thanks for your submissions and new features!

And of course, anyone can voluntarily join the release team, and if
you're a committer on the project I'll be coming to see if you can take
specific QA tasks when we cut the first RC next week.

Regards,

Chris

-- 
Christopher Brooks, BSc, MSc
ARIES Laboratory, University of Saskatchewan

Web: http://www.cs.usask.ca/~cab938
Phone: 1.306.966.1442
Mail: Advanced Research in Intelligent Educational Systems Laboratory
     Department of Computer Science
     University of Saskatchewan
     176 Thorvaldson Building
     110 Science Place
     Saskatoon, SK
     S7N 5C9
_______________________________________________
Matterhorn mailing list
[email protected]
http://lists.opencastproject.org/mailman/listinfo/matterhorn


To unsubscribe please email
[email protected]
_______________________________________________

Reply via email to