[Scons-dev] SCons.. the road ahead

William Blevins wblevins001 at gmail.com
Fri Sep 25 18:16:12 EDT 2015


I don't see that being a priority.  We were just agreeing that we could
start doing cleanup.

On Fri, Sep 25, 2015 at 11:13 PM, Alexandre Feblot <alexandre at feblot.fr>
wrote:

> Hi,
> Wasn't Dirk speaking of first cleaning some 2.6-ish code?
>
> *--*
> Alexandre Feblot
>
> Le 26 sept. 2015 à 00:02, William Blevins <wblevins001 at gmail.com> a écrit
> :
>
>
>
> On Fri, Sep 25, 2015 at 10:57 PM, Bill Deegan <bill at baddogconsulting.com>
> wrote:
>
>>
>>
>> On Fri, Sep 25, 2015 at 2:50 PM, William Blevins <wblevins001 at gmail.com>
>> wrote:
>>
>>>
>>>
>>> On Fri, Sep 25, 2015 at 10:40 PM, Bill Deegan <bill at baddogconsulting.com
>>> > wrote:
>>>
>>>> Greetings,
>>>>
>>>> Here's what I'm thinking (Note I'm explicitly not discussing any
>>>> infrastructure changes here, bugtracker, git vs hg, etc, so please do not
>>>> chime in in this thread on those issues)
>>>>
>>>> 1) Merge any fairly trivial pull requests currently outstanding to
>>>> default branch
>>>> 2) Release 2.4.1 (And push to pypi)
>>>> 3) Merge cross language scanner pull request.
>>>> 4) Release 2.5.0 (and push to pypi)
>>>>
>>>
>>> I follow you up to here.
>>>
>>>
>>>> 5) Merge 3.0 branch to default and finish that once and for all.
>>>>
>>>
>>> Is this part high risk?  I assume that the 3.0 branch is still 2.7
>>> compliant.  If it is then, it should be fine.
>>>
>>
>> Yes the codebase should be Python 2.7.x and 3.x compat (where x is TBD
>> but most likely .10 and .3? respectively).
>>  No Python 3.x only SCons for the foreseeable future, at least in my
>> mind. Enough people are stuck at that with platforms they need to support
>> for a while.
>>
>
>
> Then I don't see any issues with this path forward.
>
>>
>>
>>>
>>>
>>>> 6) Release a beta for 3.0
>>>> 7) Release 3.0
>>>>
>>>> Thoughts?
>>>>
>>>> -Bill
>>>> SCons Project Co-Manager
>>>>
>>>>
>>>> _______________________________________________
>>>> Scons-dev mailing list
>>>> Scons-dev at scons.org
>>>> https://pairlist2.pair.net/mailman/listinfo/scons-dev
>>>>
>>>>
>>>
>>> _______________________________________________
>>> Scons-dev mailing list
>>> Scons-dev at scons.org
>>> https://pairlist2.pair.net/mailman/listinfo/scons-dev
>>>
>>>
>>
>> _______________________________________________
>> Scons-dev mailing list
>> Scons-dev at scons.org
>> https://pairlist2.pair.net/mailman/listinfo/scons-dev
>>
>>
> _______________________________________________
> Scons-dev mailing list
> Scons-dev at scons.org
> https://pairlist2.pair.net/mailman/listinfo/scons-dev
>
>
>
> _______________________________________________
> Scons-dev mailing list
> Scons-dev at scons.org
> https://pairlist2.pair.net/mailman/listinfo/scons-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://pairlist2.pair.net/pipermail/scons-dev/attachments/20150925/6f644270/attachment.html>


More information about the Scons-dev mailing list