2009/3/8 chromatic <[email protected]>: > On Sunday 08 March 2009 07:25:40 Reini Urban wrote: > >> Breaking our cross-version policy???? >> >> First letting platform portability go, and now also versions? > > Please read our support policy regarding bytecode changes and deprecation > cycles.
pdd13_bytecode.pod: A single version of Parrot can support reading and writing of more than one bytecode file format. In fact, once Parrot is in production use it will be preferable to write as early a bytecode format as is possible, to allow the greatest compatibility with previous Parrots. These versions are listed in the PBC_COMPAT file, sorted with the latest version first in the format: MAJOR.MINOR DATE NAME DESCRIPTION But I don't find the paragraph yet about the post-1.0 policy, not using old numbers for new pmcs and ops. It is somewhere. It should be pretty clear also that renumbering is forbidden, only adding allowed. -- Reini Urban http://phpwiki.org/ http://murbreak.at/ _______________________________________________ http://lists.parrot.org/mailman/listinfo/parrot-dev
