[Jython-checkins] SF.net SVN: jython: [3558] trunk/website/Project/roadmap.txt

[<fwi...@us...>]

Revision: 3558
          http://jython.svn.sourceforge.net/jython/?rev=3558&view=rev
Author:   fwierzbicki
Date:     2007-10-04 10:13:42 -0700 (Thu, 04 Oct 2007)

Log Message:
-----------
changed to reflect current thinking.

Modified Paths:
--------------
    trunk/website/Project/roadmap.txt

Modified: trunk/website/Project/roadmap.txt
===================================================================
--- trunk/website/Project/roadmap.txt	2007-10-03 09:02:52 UTC (rev 3557)
+++ trunk/website/Project/roadmap.txt	2007-10-04 17:13:42 UTC (rev 3558)
@@ -17,34 +17,14 @@
 Jython  2.2
 ===========
 
-A first beta has been released towards Jython-2.2.  A second beta is
-needed to address a couple remaining issues in the new-style class integration:
+Jython 2.2 has been released.  We are also producing point releases
+for bug fixing.
 
-1. The tool output from Pedroni's program referenced at
-http://sourceforge.net/mailarchive/message.php?msg_id=37797385
-shows several differences between Jython's type hierarchy and that of
-CPython's as well as highlighting the lack of many of the
-rich-comparision operators on our built-in types.  Both of these need
-to be fixed before beta 2.
-
-2. We need to get more of test_descr working.  Charlie Groves has 
-created bug reports for most of the remaining work for test_descr.
-
-Once those two items are resolved, a second beta will be released, and
-then we'll move on to the release of 2.2 final.  For 2.2 we will not be
-considering much beyond these problems.  Bugs will be looked at on a
-case by case basis and many will not be fixed for 2.2.  Jython in its
-current state is quite fragile, and fixing one bug often leads to many
-more.
-
-Jython 2.4 or 2.5
+Jython 2.5
 ==========================
 
 Jython's current fragility means that the next release will primarily
-be a cleanup release.  We will probably target
-either Python 2.4/2.5, although we might even consider 2.5, as it would
-be great to catch up, and the changes in the core language in the 2.x
-series at this point are fairly small.
+be a cleanup release.  The current plan is to target Python 2.5.
 
 We have noticed that the current codebase is
 extremely brittle and uses way to many different styles to do many of
@@ -53,31 +33,21 @@
 extraordinarily difficult.
 
 This means that, at least for the core developers, we will be
-concentrated on making a clean 2.4/2.5, while improving the java
-integration, but will not be spending much time trying to get CPython
-frameworks working.  Also, we will not be considering any big changes
-to the core (such as using ASM for bytecode generation) and will not
-be considering code changes just to improve performance.
+concentrating on making a clean 2.5, while improving the java
+integration.  An earlier version of this doc suggested that
+we would not be considering moving to ASM or Antlr -- but a very
+successful Google Summer of Code project and much committer interest
+has made it quite likely that we will do just that (move to ASM
+and Antlr).
 
-This does not mean that I want to discourage experimentation with
-CPython frameworks.  I think after we have done some house cleaning
-that CPython frameworks are the next target.  I'm just saying that
-this will not be the focus of the next release.  Making the codebase
-more consistent and accessible will be the primary focus.
+A side goal of Jython 2.5 is to try to get some CPython frameworks working,
+especially the web frameworks, for example:
 
-Of course, once we have a 2.4/2.5 release, then we can really look at
-the issues above (CPython frameworks, performance, big changes to the
-core, etc) and I believe we will have a much better chance for
-success.
+* Django
+* Pylons
+* TurboGears
+* Twisted
 
-Next Jython 2.x
-===============
-
-This release will build on the cleanup in the last release, and in this
-release we will be able to consider performance enhancements, CPython
-frameworks, and other considerations that where shelved for the last
-release.
-
 Jython 3.0
 ==========
 
@@ -91,34 +61,3 @@
 Serious discussions about Jython 3.0 can perhaps begin once CPython 3.0
 goes to a GA release.
 
--------
-Details
--------
-Below is a start at dividing the issues that may be addressed by future Jython releases.  The items listed here are just a beginning, they are not gaurantees.  We will certainly add and remove items as things progress.  I have labeled them "Jython 2.4", "Jython 2.6" and "Jython 3.0" (based on the version of CPython that will be targetted), although the exact versions are up for discussion (for example, Jython 2.4 may be re-targetted at 2.5).
-
-Jython 2.4
-==========
-
-Clean up is the primary goal of this release, though some enhancements will happen as well (incorporate CPython core language changes and improve Java integration).
-
-Clean up
---------
-
-* All fundemental classes should be converted to new-style classes.
-
-Enhancements
-------------
-
-* method dispatch should be an Java implementation of Samuele's Jython prototye.
-
-Jython 2.6
-==========
-The primary goal of Jython 2.6 will be the enabling of CPython frameworks, especially the web frameworks.  I would like to see at least the following frameworks functioning:
-
-* TurboGears
-* Django
-* Twisted
-
-Jython 3.0
-==========
-TBD


This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.