Heather Stephens wrote on Monday, October 11, 2004 8:45 PM: > 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 Since there are a few sessions at Apache on Beehive topics, it definitely seems like it would be good for attendees to be able to download the same set of bits that the speakers refer to in their sessions. On the topic of requirements for incubating projects doing releases, see http://nagoya.apache.org/eyebrowse/[EMAIL PROTECTED]&msgNo=3719 for some comments I once made to the MyFaces folks about what is required of releases. Basically, we need 1) a vote of the Beehive PPMC, which includes interested Incubator PMC members; 2) the word "incubating" in the filenames of the downloads; and 3) a disclaimer paragraph in the README file and near the actual download link on the web site. > Question 2 --> In the spirit of the X.y.z naming convention and > assuming we will do a few of these before we cut V 1.0.z with a 0.5.z > beta-quality release, shall we name an ApacheCon release as version > 0.3.z? +1 > 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 all looks good to me
