Question 1: +1 Question 2: +1 Question 3: +1 I think it is vital that we begin to converge towards a 1.0 release so real users can build (and deploy) real apps, and putting out a 0.8 release sooner rather than later shows we are serious and starts the convergence process.
-- Kyle > -----Original Message----- > From: Ken Tam > Sent: Tuesday, February 15, 2005 4:36 PM > To: Beehive Developers > Subject: [proposal] Beehive Beta1 public distribution release > > We should do a Beta1 public distribution release. Here's why: > > a) Beehive as essentially feature complete for v1 -- on that basis alone > it seems an appropriate time to release another public distribution. > While I don't think we're prepared to unequivocally state that APIs are > actually frozen, it's fair to say that we expect only minor changes > between now and GA. > b) The last distribution release we did was several months ago (alpha) > and we've made huge strides since then. A release now will make it much > easier for users to engage and provide a formal label for filing > issues/having discussions. > c) EclipseCon and TheServerSide Symposium are both just around the > corner, it would be great to have fresh downloadable bits available in > time for that (Feb 28-Mar 3, Mar 3-5 respectively). > > Question 1: > Should we aim to produce a public distro release for Feb 28/2005? > > Question 2: > Shall we call it Beta1 and version it as 0.8.z? We're definitely closer > to the end than to the beginning. > > Question 3: > Can we agree on the following goals for this release? > > Goals: > Feature complete > APIs highly stable (weak guarantee of back compat) > Updated docs/samples > Provide a reference point for bug reporting/discussion > Dogfoodable for app building > > Non-goals: > Strong guarantee of backwards compat > Usable for production > Completed docs/samples > > Please vote ASAP, we do not have a lot of time to do this :) > > Thanks! > >
