COmanage Developers List

[Digant C Kasundra <>]

What do we do when we get to X?  :)

----- "Heather Flanagan" 
<>
 wrote:

> RL 'Bob' Morgan wrote:
> >
> > Sorry for getting overexcited on the call today, no offense
> intended.
> >
> > One thing occurred to me as we speculated about what might get 
> > released when I became confused about "this one" and "next one". 
> I'm 
> > a little uncomfortable with the usual alpha/beta terminology for
> this 
> > product in particular, maybe because it's so much a packaging of
> other 
> > things with their own versions.  I wondered whether following the 
> > practice of projects like, well, Debian, with named releases might 
> > both help the project focus on which-release-when and avoid the 
> > implied readiness-for-use of alpha/beta.  So, for example, the
> project 
> > could define features for the "Palindromic Panda" release with a 
> > target of March 2009, and a future "Oleaginous Ocelot" release with
> a 
> > target of Fall 2009 with other features.  Then a release could be 
> > characterized as "only for testers" or "ready for COs" or similar. 
> 
> > Appealing?
> >
> >  - RL "Bob"
> 
> Hugely appealing, actually!  It both makes sense and appeals to my
> funny 
> bone.  :-)
> 
> -hf

-- 
Digant C Kasundra 
<>
Technical Lead, ITS Unix Systems and Applications, Stanford University