Differences between revisions 14 and 17 (spanning 3 versions)
Revision 14 as of 2008-02-11 06:27:36
Size: 3458
Comment:
Revision 17 as of 2008-02-15 19:51:42
Size: 3922
Editor: 133
Comment: Typo fix.
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
This is a specific list of the features needed to make releases towards Jython 2.5. The first alpha will be made once Jython supports all CPython 2.5 language level features. After the alphas have stabalized, all the library and Jython-only features will be completed in the beta series of releases. Once all the features are present in the betas, we'll go into release candidate mode until 2.5 is finally released. This is a specific list of the features needed to make releases towards Jython 2.5. The first alpha will be made once Jython supports all CPython 2.5 language level features. After the alphas have stabilized, all the library and Jython-only features will be completed in the beta series of releases. Once all the features are present in the betas, we'll go into release candidate mode until 2.5 is finally released.

Just because a feature is in the beta list, that doesn't mean it can't land before the alpha release. It only means it isn't necessary before the alpha. Actually since all of the alpha features are dependent on the new compiler and parser, the beta tasks can be a good starting point. PEPs 292, 305, 324 and 327 should be doable with trunk as can the template removal tasks and bugtests migration at the end of the list.
Line 51: Line 53:
 * Import Python from the classpath

This is a specific list of the features needed to make releases towards Jython 2.5. The first alpha will be made once Jython supports all CPython 2.5 language level features. After the alphas have stabilized, all the library and Jython-only features will be completed in the beta series of releases. Once all the features are present in the betas, we'll go into release candidate mode until 2.5 is finally released.

Just because a feature is in the beta list, that doesn't mean it can't land before the alpha release. It only means it isn't necessary before the alpha. Actually since all of the alpha features are dependent on the new compiler and parser, the beta tasks can be a good starting point. PEPs 292, 305, 324 and 327 should be doable with trunk as can the template removal tasks and bugtests migration at the end of the list.

Alpha

Done

Beta

RoadMap (last edited 2013-02-06 23:22:57 by FrankWierzbicki)