For what it's worth, I think an interim release would be a great thing,
no matter how oddball the feature set (I'd suggest calling it 2.2pre1).
It would be very nice to get something on the Jython page that showed
current activity. Also valuable would be a road map matching
outstanding tasks with future pre releases. I think that packaging
interim releases more frequently would be very valuable, especially in
cutting down the "Is Jython alive..." messages on this list.
I think there are a lot of people on this list who would be willing to
help out in putting a release together (either on bug fixes, or release
management, or whatever) if we could get a good sense of exactly what
needed to be done. In other words, how can we help?
Samuele Pedroni wrote:
>From: "Kevin Butler" <jython-kbutler@...>
>>I think we should put together a release of the post Jython 2.1,
>>pre-Jython 2.2 development, both to help abate the "is it dead?"
>>questions and also to give easier access to the useful development that
>>has occurred since 2.1 was released.
>>I'd suggest calling it something like Jython 2.1.5, or 2.1+1, or some
>>such, to make it clear that development has proceeded beyond 2.1.
>>Another option could be 2.2pre1, though that may suggest we are nearly
>>feature complete for Python 2.2. (An outstanding task list would be
>>helpful - anyone?)
>My opinion remains the same, the most meaningful thing would be a bug-fix-only
>2.1.1 release, but:
>- Sadly we didn't plan for that: in the commits - I think - bug fixes and new
>features are rather mixed up.
>- We have more commited new features but still a lot of pending even trivial
>bugs, and anyway some java intergration bugs are best left untouched given the
>reworkings needed for class/types unification.
>- Nobody has shown interest in doing this heartless task.
>So the bug-fix-only release is wishful thinking. So obviously I'm not going to
>stop you :)
>For an interim release:
>- It should be very clear which 2.2 features are supported and which not,
>otherwise we will have a lot of questions: in particular jythonc is basically
>still in its 2.1 shape. How to support generators, class/types unification and
>how to solve its maintainance problems is an open issue.
>- Apart from the liveliness showing, how many people are interested for serious
>work in an oddball package of partial 2.2 features and pending bugs?
>- bug fixing
>- see the task manager:
>- 2.2 and 2.3 PEPs: 264, 302...
>Generators in the interpreter are mostly finished, and the list archives
>contain the discussion about what is left to do and how to do it.
>Technically: the major problem for such an interim release is that one cannot
>simply ship the 2.2 std lib but one should pick from both the 2.1 and 2.2,
>because some modules e.g. pickle and related in 2.2 depend on class/type
>unification which is still a pending task. So one should carefully use the test
>suite to pick the modules and sort out possible dependencies issues.
>>What else do I need to do to create an interim release? (I'm looking at
>>the installer subdirectory, anything else?)
>No matter what, a streamlined document on how to produce a release would be
>very valuable, Finn at the moment is the repository of such knowledge.
>>Used for python library (?)
>see remark above.
>This SF.net email is sponsored by: ValueWeb:
>Dedicated Hosting for just $79/mo with 500 GB of bandwidth!
>No other company gives more support or power for your dedicated server
>Jython-dev mailing list