At 11:41 AM 8/29/2006 -0700, Heikki Toivonen wrote:
So, to start with milestone schemes... Chandler currently is proceeding
towards 0.7 Release (0.7alpha1, 0.7alpha2, ... 0.7alpha6, 0.7 Release).
Actually there is also a question: should the 0.7 Release be called 0.7beta?
No. :)
Once Chandler reaches 0.7 Release, which we also call the Chandler Beta,
We should stop that; it's not a web service but a release, so it should go
by the release number.
are we going to continue with 0.8alpha1, ... or will that change to
0.8beta1?
No, it should not change.
Note, however, that all of my answers are from a tech perspective rather
than a marketing one. If we're talking marketing then all bets are
off. ;) However, for clarity within the organization and with community
developers the terminology should be consistent, and calling 0.7 "Chandler
Beta" nickname for 0.7 is right out. "Public test", "Preview", "Early
Access", or some other suitable name should be used, since it is neither a
traditional (i.e. feature complete) beta release nor a "continuous beta"
web service. Coining a third and altogether new meaning for "beta" seems
likely to cause confusion... No, strike that. The fact that you're
posting these questions means it already *has* created confusion. :)
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "General" mailing list
http://lists.osafoundation.org/mailman/listinfo/general
