[Scons-dev] Should we close python3-port branch in scons bitbucket?

Bill Deegan bill at baddogconsulting.com
Thu Apr 14 12:45:48 EDT 2016


Russel,

I guess the other question is the python3-port branch in scons' repo an
earlier version of your branch?
Or is your branch entirely different?

-Bill

On Thu, Apr 14, 2016 at 12:29 PM, Bill Deegan <bill at baddogconsulting.com>
wrote:

> Russel,
>
> So the branch your work is on in your repo is python3-port?
>
> I'm o.k. with CI going red for this. I don't want to delay the python 3
> port any further.
> I think the project should go "all in" on getting py2/3 done at this point
> in time.
>
> How long would you expect getting your py3 work to run/pass all tests on
> py2.7?
> (Wild guesses are welcome)
>
> -Bill
>
>
>
> On Thu, Apr 14, 2016 at 10:46 AM, Russel Winder <russel at winder.org.uk>
> wrote:
>
>> Bill,
>>
>> It is also worth thinking about the "CI shall never go red" vibe.
>> Currently my python3-port branch is very red.
>>
>> --
>> Russel.
>>
>> =============================================================================
>> Dr Russel Winder      t: +44 20 7585 2200   voip:
>> sip:russel.winder at ekiga.net
>> 41 Buckmaster Road    m: +44 7770 465 077   xmpp: russel at winder.org.uk
>> London SW11 1EN, UK   w: www.russel.org.uk  skype: russel_winder
>>
>> _______________________________________________
>> 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/20160414/17256cdd/attachment.html>


More information about the Scons-dev mailing list