Re: 2.7.2 for the New Year?

Thanks Frank. 2nd or 27th Feb, perhaps.

As you're the expert in this, can//I ask //am I doing this right (in 
build.xml, obviously):

         <!-- The current version info -->
         <property name="jython.version" value="2.7.2a1"/>
         <property name="jython.version.noplus" value="2.7.2a1"/>
         <property name="jython.major_version" value="2"/>
         <property name="jython.minor_version" value="7"/>
         <property name="jython.micro_version" value="2"/>
         <property name="jython.release_level" 
value="${PY_RELEASE_LEVEL_ALPHA}"/>
         <property name="jython.release_serial" value="1"/>

In history, I see we commit this type of change, then there's a commit 
with a tag. Am I able to push a change that adds a tag? ISTR there's a 
restriction.

When do we add the + to a version? (We seem to have forgotten so far in 
2.7.1.) Does the plus have a magical effect somewhere?

Jeff

Jeff Allen

On 22/11/2017 19:42, [email protected] wrote:
> A new year's 2.7.2 with a limited scope is definitely a great idea, as
> is an updated GitHub based website. I'm on board!
>
> -Frank
>
> On Tue, Nov 21, 2017 at 3:32 PM, Jeff Allen <[email protected]> wrote:
>> 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
>> _______________________________________________
>> Jython-dev mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/jython-dev

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

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