Re: [Proposal] Milestone and general naming, terminology

Ted Leung <twl-6zGkXsw2EZWGJGYlWa3Ukdi2O/[email protected]>
Newsgroups gmane.org.osaf.general
Message-ID <[email protected]>
+1:  I prefer preview to beta.

On Sep 6, 2006, at 4:51 PM, Katie Capps Parlante wrote:

> Based on everyone's feedback, it sounds like we should go with  
> Philippe's proposal...
>
> Philippe Bossut wrote:
>> Conclusion, I'm inclined to:
>> - replace our use of "beta" by "Preview" for all our marketing  
>> communication
>> - use "dogfood" internally when talking about our "alpha" milestones
>> - not change our use of "alpha" by something else in our numbering  
>> scheme
>
> For Chandler, that would mean sticking to the current numbering  
> system.
>
> 0.6 (Dogfood)
>   ...
>   0.7alpha4
>   0.7alpha5
>   0.7alpha6
> 0.7 (First Preview)
>   0.8alpha1
>   0.8alpha2
>   ...
> 0.8 (Second Preview)
>   ...
> 1.0
>
> For Cosmo, that means the project would be free to *not* use the  
> "alpha" term for interim milestones if that is not appropriate.  
> Some near release would be labeled "Dogfood" (at least for a  
> certain set of end-user features) and another release in the March  
> timeframe would be labeled "Preview".
>
> "Dogfood" ==> usable inside of OSAF
> "Preview" ==> solid and complete enough for some feature set to be  
> usable by people outside of OSAF
>
> Jared, your concerns about "Preview" not sending the right message  
> do give me pause; I am won over by Pieter's argument that producing  
> a release that someone will find useful will be the more  
> significant factor here. :)
>
> Cheers,
> Katie
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
>
> Open Source Applications Foundation "General" mailing list
> http://lists.osafoundation.org/mailman/listinfo/general

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

Open Source Applications Foundation "General" mailing list
http://lists.osafoundation.org/mailman/listinfo/general
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.