From 626c4d415b79790df1872788b9e2412523afa870 Mon Sep 17 00:00:00 2001
From: Galen Charlton <gmcharlt@gmail.com>
Date: Fri, 27 Apr 2012 21:40:55 -0400
Subject: [PATCH] start EGConf12 dev update slides

Signed-off-by: Galen Charlton <gmcharlt@gmail.com>
---
 egconf12_dev_update.txt | 106 ++++++++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 106 insertions(+)
 create mode 100644 egconf12_dev_update.txt

diff --git a/egconf12_dev_update.txt b/egconf12_dev_update.txt
new file mode 100644
index 000000000..3f078bd87
--- /dev/null
+++ b/egconf12_dev_update.txt
@@ -0,0 +1,106 @@
+Developer's update -- Evergreen Conference 2012
+===============================================
+:backend: slidy
+:data-uri:
+:icons:
+
+Overview
+--------
+
+- RM & RMaints
+- Evergreen 2.3
+- Path to Evergreen 2.2.0
+- Evergreen 2.1.x
+- Google Summer of Code
+- What's in 2.2.0
+- The future
+
+Releases
+--------
+
+- One basic question: what will we get?
+- Second basic question: when, already?
+
+We have a better handle on what... when, needs work.
+
+[role="incremental"]
+**Time-based releases**
+
+Time-based releases
+-------------------
+
+**The goal**
+
+. Two major release a year, six months apart.
+
+[role="incremental"]
+__March and September?__
+
+. Bugfix releases on a periodic schedule
+
+[role="incremental"]
+__Every month?__
+
+Release Manager
+--------------
+
+Responsible for making sure quality releases get made on
+time.
+
+[role="incremental"]
+
+**Not** single-handedly
+
+RM Responsibilities
+-------------------
+
+- Propose release schedule
+- Be final, neutral technical arbiter of what does or does not make it into a release
+- Help coordinate the efforts of coders and testers to make sure that patches are looked at on a timely basis
+- Be the designated tie-breaker
+
+[role="incremental"]
+**AND**
+
+[role="incremental"]
+- __Regularly__ communicate the status of the release
+  to the rest of the community
+
+Term
+----
+
+- Chosen among the active committers; currently
+  by developer consensus.
+- Term is until the release of X.Y.0
+- After the release, time to choose the next RM
+
+Release Maintainer
+------------------
+
+- Does most of what the release manager does, but for
+  bugfix releases.
+- There __can__ be more than one
+- Chosen among the active committers and developers
+
+Evergreen 2.3
+-------------
+
+Introducing Release Manager Bill Erickson
+
+Path to Evergreen Evergreen 2.2.0
+---------------------------------
+
+Introducing Release Maintainer Lebbeous Fogle-Weekly
+
+- Bug triage over next few days
+- 
+Evergreen 2.1
+-------------
+
+Introducing Release Maintainer Dan Scott
+
+What's in 2.2.0
+---------------
+
+The future
+----------
-- 
2.11.0