RFC: Release team meetings

[Toshio Kuratomi]

On Fri, 2007-04-13 at 07:05 +0200, Thorsten Leemhuis wrote: 
> +1 -- but it might be good to bring important topics up in the FESCo
> meetings -- similar how Packaging Committee or EPEL topics sometimes get
> brought up now. That requires that the "Release team" writes proper
> minutes of their decisions and doings.

I agree.  Information flow is extremely important.  Note that I think
the Packaging Committee is not a good model for the release team,
though.  The PC isn't just reporting to FESCo, we're also having our
items approved.  As a FESCo member, I envision the releng team having
broader powers to do things first and report on them after.

There _will_ be contentious issues and a way of dealing with them needs
to be figured out.  I think a retrospective look on how cvs ACLs and the
new review processes were created, how they were decided, how they felt
to someone outside the decision making process, and whether they were
implemented in a timely fashion would be a good place to find ideas on
how to make things both efficient and keep everybody feeling involved
and empowered.

On Fri, 2007-04-13 at 09:04 -0400, Jesse Keating wrote:
> On Friday 13 April 2007 01:05:05 Thorsten Leemhuis wrote:
> > I'd further would like to see more informations what the Release Team is
> > (number of people and names), how it is constituted (approved, elected,
> > mixed?), who's responsible (chairmen?) and what its works areas exactly
> > are (what remains FESCo work and what will the Release Team take care
> > of? and when does the Board get into the game?).
> 
> It's things like this that start to frustrate me.  Sure it's neat information 
> to have, but for the sake of getting a few people together to get some work 
> done, I really don't want to have to go through the headache of creating all 
> this red tape and governance.

I don't think there needs to be a lot of governance, just some
information on who's doing what.  Jesse, Thorsten, releng team, what do
you think of this proposal:

---

= Release Engineering Team =

== Composition ==
 * Jesse Keating (f13)
 * Josh Boyer (jwb)
 * Bill Nottingham (notting)
 * Jeremy Katz (katzj)
 * [Please fill in and correct]

Release Team members are approved by FESCo.  However, FESCo has
delegated this power to the Release Team itself.  If you want to join
the team, contact releng at fedoraproject.org.

== Who's in Charge ==
Jesse Keating.  Leadership is currently appointed by FESCo with input
from the current release team.

== Things we Do ==
 * Set the schedule for releases including freeze dates, final release,
slips, etc.
 * Set blocker criteria for the release.
 * Decide what packages go onto a spin.
 * Create official Fedora Spins.
 * Report progress towards release from Feature Freeze on.
 * Give reports to FESCo on changes to processes.
  * If something is known to be controversial, we let FESCo know before
implementing otherwise implementation generally happens concurrently to
reporting.
 * [Fill in anything related to release management you want]

== Where we do it ==
 * IRC: [Select an IRC Channel]
 * Mailing List: releng at fedoraproject.org
 * Meetings: Not currently.  We just discuss things on [IRC channel]
when we think of something. [If Bill's meeting plan comes to fruition,
add a link and general information here]

------

Action Items:
* Have releng fill in all the bracketed items.
* Have releng team +1 this :-)
* Have FESCo +1 this
* Change releng at fedoraproject.org from an alias to a mailing list so
there's an archive of past discussions to look at.

-Toshio
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://lists.fedoraproject.org/pipermail/advisory-board/attachments/20070413/e9ba65f9/attachment.bin