+1 from me, Ias
> -----Original Message----- > From: Richard Feit [mailto:[EMAIL PROTECTED] > Sent: Tuesday, October 26, 2004 9:41 PM > To: Beehive Developers > Subject: Re: [Result] Pre-V1 release for ApacheCon? > > +1 > > Heather Stephens wrote: > > >I think we should call it alpha. Calling it "ApacheCon > 2004" doesn't > >really give any indication to our users about our > expectations of the > >distribution. > > > > > > > >-----Original Message----- > >From: Ken Tam > >Sent: Tuesday, October 26, 2004 11:36 AM > >To: Beehive Developers > >Subject: RE: [Result] Pre-V1 release for ApacheCon? > > > >Heather, can you create an "ApacheCon 2004" version in JIRA and > >bulk-edit the issues that are currently set to "TBD"? > Owners can then > >assign out to Version 1 as appropriate. > > > >Thanks! > > > >-----Original Message----- > >From: Heather Stephens > >Sent: Tuesday, October 19, 2004 12:51 PM > >To: Beehive Developers > >Subject: [Result] Pre-V1 release for ApacheCon? > > > >Let's go for it... > > > >*11 of 24 committers voted. (~50% are actively contributing to the > >current code base) > > > >*11 of 11 voted +1. > > > >*3 people in the community responded with +1 love. > > > > > > > >-----Original Message----- > >From: Steve Hanson > >Sent: Tuesday, October 19, 2004 11:56 AM > >To: Beehive Developers > >Subject: RE: [Proposal] Pre-V1 release for ApacheCon? > > > >Sorry for the late response... > >+1 > > > >-----Original Message----- > >From: Steven Tocco > >Sent: Tuesday, October 19, 2004 10:58 AM > >To: Beehive Developers > >Subject: RE: [Proposal] Pre-V1 release for ApacheCon? > > > > > >+1 > > > >-----Original Message----- > >From: Heather Stephens > >Sent: Tuesday, October 19, 2004 10:14 AM > >To: Beehive Developers > >Subject: RE: [Proposal] Pre-V1 release for ApacheCon? > > > >5 of 24 committers voted. > >5 of 5 voted +1. > >Of those 24 committers, around 50% are actively participating. > > > > > >Rotan, Ias, Michael, Steve H., Daryl, Steve, James, Eddie -- what do > >you say to driving towards a release at ApacheCon? > > > > > >If a simple majority of active committers wants to do this, > I think we > >should go for it. > > > > > > > >-----Original Message----- > >From: Richard Feit > >Sent: Friday, October 15, 2004 11:21 AM > >To: Beehive Developers > >Subject: Re: [Proposal] Pre-V1 release for ApacheCon? > > > >+1 > > > >I think we need to have a release before ApacheCon in order > to get the > >framework out to people who want to try it... unless it's > impossible to > >drive to a stable one in that timeframe (and I definitely > don't think > >it > > > >is). > > > >Kyle Marvin wrote: > > > > > > > >>+1 on doing a release for ApacheCon > >> > >> > >> > >> > >> > >>>-----Original Message----- > >>>From: Heather Stephens > >>>Sent: Friday, October 15, 2004 12:51 PM > >>>To: Beehive Developers > >>>Subject: RE: [Proposal] Pre-V1 release for ApacheCon? > >>> > >>> > >>>We've gotten response from Cliff and Ken. IMO that isn't > enough to > >>>push us to a release for ApacheCon. Does anybody else have an > >>>opinion or should we kill this proposal now? > >>> > >>>-----Original Message----- > >>>From: Ken Tam > >>>Sent: Wednesday, October 13, 2004 8:21 PM > >>>To: Beehive Developers > >>>Subject: RE: [Proposal] Pre-V1 release for ApacheCon? > >>> > >>> > >>> > >>> > >>> > >>>>-----Original Message----- > >>>>From: Heather Stephens > >>>>Sent: Monday, October 11, 2004 8:45 PM > >>>>To: Beehive Developers > >>>>Subject: [Proposal] Pre-V1 release for ApacheCon? > >>>> > >>>>Question 1 --> Should we shoot to do a pre-V1 release of > Beehive for > >>>>ApacheCon? (NOTE: We would also need Incubator PMC approval for > >>>>this of course.) > >>>> > >>>> > >>>> > >>>> > >>>+1, I think the timing is ideal for a release. > >>> > >>> > >>> > >>> > >>> > >>>>Question 3 --> Proposal on Goals/Non-goals ============== Goals > >>>>============== *Practice the release process so we can > begin to work > >>>>out the kinks *Binary distribution available *"Demoable" for > >>>>ApacheCon 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 on the current feature set. > >>>> > >>>>============== > >>>>Non-goals > >>>>============== > >>>>*Feature complete > >>>>*APIs locked > >>>>*Beta-quality > >>>>*Guarantee of backwards compat > >>>> > >>>> > >>>> > >>>> > >>>+1, we're overdue to start driving on these goals. > >>> > >>> > >>> > >>> > >>> > >>> > >>> > >> > >> > >> > >> > > > > > > > > > > > > > > > > > > >
