You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@beehive.apache.org by Heather Stephens <he...@bea.com> on 2004/11/02 18:53:55 UTC
REMINDER -- Rampdown to ApacheCon and Alpha
REMINDER: Today is the day we're shooting for to pick an alpha RC rev
number.
-----Original Message-----
From: Heather Stephens
Sent: Thursday, October 28, 2004 11:40 AM
To: Beehive Developers
Subject: Rampdown to ApacheCon and Alpha
Here's a timing guideline to lead us to our V1 alpha release. I backed
into it assuming we need to ship by 11/12/2004 to hit ApacheCon.
At the bottom of this email is a reminder of our goals and non-goals for
this alpha release.
http://wiki.apache.org/beehive/ApacheCon2004?action=show
=========================
Timing guideline
=========================
10/27/2004 -- Branch
10/29/2004 -- Review doc, sample and tutorial materials for
completeness, functionality and accuracy.
10/31/2004 -- Known dev and docs/samples/tutorials work that is included
in the distribution complete. Checkin test pass. Additional test
suites have been run along the way. Folks doing sessions & demos at
ApacheCon believe the code base is in good shape. Egregious "can't ship
without" bugs on alpha quality have been filed.
11/1/2004 -- Fix any last minute items.
11/2/2004 -- Choose changelist as distribution and begin final test
passes
11/8/2004 (latest) -- Call official vote on V1 alpha release (choose a
revision number as a candidate for the alpha distribution)
11/10/2004 EOD -- Close vote
11/11/2004 -- Tally votes, send results, roll and sign distribution,
send announcement emails to Apache lists
=========================
Release Goals/NonGoals
=========================
Goals
** Practice the release process so we can begin to work out the kinks
** Binary distribution available
** Demoable for conference sessions
** Enough supporting materials (sample applications, feature samples,
documentation, tutorials, etc.) to generate interest in Beehive, begin
to build a more active user community and get useful feedback on the
current feature set.
Non-goals
** Feature complete
** APIs locked
** Beta-quality
** Guarantee of backwards compat