On Mon, Mar 09, 2009 at 01:03:24PM +0100, Reini Urban wrote:
> 2009/3/9 <[email protected]>:
> > Author: allison
> > Date: Mon Mar 9 01:56:58 2009
> > New Revision: 37222
> > URL: https://trac.parrot.org/parrot/changeset/37222
> >
> > Log:
> > [cage] Delete reference to ancient and long-abandoned bytecode policy,
> > to avoid confusing new contributors.
>
> So since when are we in production? My understanding is that the first
> production release starts with 1.0
According to the long-term roadmap [1], the first "production ready"
release is in January 2010.
[1] https://trac.parrot.org/parrot/wiki/ParrotLongTermRoadmap
> The pbc designers thought about that long and hard, and set a date
> when these random changes should stop and should be exchanged
> about a support policy which should help keeping backwards portability.
That date was set as "once Parrot is in production use", which is
January 2010. See above.
> With this change of yours we've finally lost all what the designers planned
> in the beginning.
False. See above.
> Shouldn't we postpone the first production release then to eg. 2012 and tell
> the users that we are not ready yet, and that we still want to jungle
> the ops and pmc indices around?
We aren't "postponing" the first production release -- we've already declared
it to be January 2010. See above.
> Note that all these policies only require documentation changes.
With the exception of ops.num (which allison just changed), all of the
documentation is already correct. In particular, the support_policy.pod
document outlines our current policy on bytecode.
Pm
_______________________________________________
http://lists.parrot.org/mailman/listinfo/parrot-dev
