2.7.2 for the New Year?

All:

How about it? This seems like a reasonable interval since 2.7.1.

Frank/Jim: would you care to set a goal? What else ought we to have in 
that release?

I think we should mean by the answer, what we'd like to see in 2.7.2b1. 
Then we only take on fixes during beta we didn't foresee or can't avoid. 
That way, we hopefully don't stay in beta very long. I'm extrapolating a 
bit from 
https://github.com/jython/devguide/blob/jython/devcycle.rst#stages 
(cloned from CPython) but it seems a good discipline to prevent late 
de-stabilising change.

Is it perhaps as important to create a revised web site to back the 
release? (We have talked about a site we can all contribute to via GitHub.)

Also, I've been meaning to ask, the current dev tip should identify as 
"2.7.1+" (not plain "2.7.1") shouldn't it? And 2.7.2a1 then 2.7.2a1+ as 
soon as we decide we're having a 2.7.2? I think I see how this works in 
build.xml.

Jeff

-- 
Jeff Allen


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot