Re: Closing out 2.7 beta 4

Jim:

Thanks for all the work that went into this succinct position report. 
I've several other things going on at the moment that leave me not much 
time for Jython, during your beta 4 window. (Better from mid Nov.) But 
I'll pick off something from your high priority set and see where it 
goes. More thoughts interspersed below.

Jeff Allen

On 13/10/2014 04:41, Jim Baker wrote:

>
>     Failing tests
>
> In general, the most important problems to be fixed are those that 
> directly tested by the regrtest. Here's is the current list of 
> failures, from regrtest itself:
>
> |      [exec] 16 fails unexpected:
>       [exec]     test_asynchat test_asyncore test_dict_jy test_email
>       [exec]     test_email_renamed test_gzip test_import test_inspect
>       [exec]     test_isinstance test_json test_socket test_ssl test_strtod
>       [exec]     test_tarfile test_univnewlines test_xmlrpc
> |
This is useful on its own! I often wonder whether what I see, mostly on 
Windows, is typical. I'm still getting a fair amount of "cannot delete" 
failure from unclosed files on Windows.

For a while someone was hosting a build-bot for us, but it became 
sporadic and has gone now. Such a thing would be useful but more so if 
we decided not to have failing tests but count skips removed as our 
measure of progress. (Skips ought not to be counted for CPython and GC 
specifics.) Is a build-bot possible?

>
>     2.7.1 Release Schedule?
>
> Since we didn't include your favorite feature or fix a challenging 
> bug, what is our plan for 2.7.1 and beyond? I think we should start 
> moving to a regular release cycle after 2.7.0 is released so that we 
> can adopt a time-based release schedule instead of one based on features.
>
...
>
> My initial thought is that we should count on having a release of 
> 2.7.1 about six months after, then possibly adjust to a yearly 
> schedule after that. I would love to hear others' opinions on this!
>
+1 on a time-based release plan. I guess it could not be a 2.7 at all 
until it had certain features, but that threshold reached, I we should 
get official version out there while our work is still warm. Apart from 
Jython, I don't download for use, anything less solid than an official 
release, so tend to think the number that take up our betas is far 
smaller than the potential user community. A year at the longest: it 
depends on our rate of work.

>
>     Jython 3.5 development plans
>
> We plan to kickoff Jython 3.5 development at the PyCon 2015 sprints in 
> Montreal; as with previous versioning,
>
...
>
> Jython 3.5 should target a minimum of Java 8; and we should upgrade to 
> using Antlr 4 for our parser support.
>
>
Ambitious! But interesting. It will be a stretch to be developing on two 
fronts: you don't have to read Python-dev for very long to be reminded 
of that.

------------------------------------------------------------------------------
Comprehensive Server Monitoring with Site24x7.
Monitor 10 servers for $9/Month.
Get alerted through email, SMS, voice calls or mobile push notifications.
Take corrective actions from your mobile device.
http://p.sf.net/sfu/Zoho

_______________________________________________
Jython-dev mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jython-dev