vision for 1.0

[Patrick R. Michaud]

On Tue, Dec 16, 2008 at 08:04:56PM -0800, Allison Randal wrote:
> I just posted on parrot.org about Parrot's new release plan, and setting 
> user expectations for the 1.0 release and beyond:

The paragraph on deprecation cycle isn't precisely how I remember it,
or at least leaves room for ambiguity.  Currently the 1.0 vision states:

    ... Starting with 1.0, the deprecation cycle will follow the 
    stable releases instead of the monthly development releases, so 
    any feature that's marked as deprecated when, for example, the 1.5 
    release is shipped, can be removed from the 2.0 release, but 
    will continue to be supported for the 6 months until the 
    2.0 release.

A clearer description might be:

    Starting with 1.0, removal of deprecated features will follow
    the stable release cycle instead of the monthly development
    releases.  Thus, any feature that is deprecated will remain
    in Parrot through at least the next stable release, after which
    it can be removed from Parrot at any time.

Overall the document looks terrific -- I think it captures the spirit
and decisions of the summit quite well.
    
Pm