On Tue, Sep 15, 2009 at 4:59 PM, Stuart Monteith <[email protected]> wrote:
<snip> >>>>>> I was wondering what people (esp. mentors) thought about that. The >>>>>> code >>>>>> itself would be like an alpha release. This would hopefully encourage >>>>>> discussion and early adoption, and possible participation. >>>>>> >> >> release often, release early :-) >> >> i don't know the code but IMHO it's worthwhile thinking about whether >> 'alpha' is really the best description >> >> for example, IMHO >> >> * kato-1.0-alpha implies that 1.0 is pretty much done but the code >> hasn't had the real life testing required to be sure that the quality >> is there. once an alpha is shipped, i would expect the code to be >> stable, with just bug fixes until a 1.0 >> * kato-0.1 implies that kato is short of features and is not mature as >> an API but that the code quality is reasonable as far as it goes >> * kato-M1 implies that kato is immature and under very active >> development but that this milestone offers an island of stability >> >> > > That last option is the most promising, I'll follow up with what I think we > should do. IIRC apache harmony uses milestones. might be worth taking a look at how they do it... - robert
