[IPython-dev] The Big Split™ has begun

[MinRK]

On Tue, Mar 24, 2015 at 5:16 PM, Wes Turner <wes.turner at gmail.com> wrote:

> A suggestion: keep the master branch relatively stable and work on a
> develop branch?
>

That is not how we are going to be doing it. Doing it that way would mean
blocking everything on master, and essentially freezing it while the
development happens, because every PR against master conflicts with the
refactor. We went over the various options, and found doing it in master to
be the least painful prospect.

-MinRK


>  The HubFlow (GitFlow) branching model solves for this:
> http://datasift.github.io/gitflow/IntroducingGitFlow.html
>
> +1 for faster tests.
> On Mar 24, 2015 6:49 PM, "MinRK" <benjaminrk at gmail.com> wrote:
>
>> We have begun the process of splitting IPython into component repos. If
>> you are living on master, it might be a good time to switch to the 3.x
>> maintenance branch, because master is going to be a bit volatile. We will
>> be aiming for a development install (pip install -e) to keep working
>> during most of this time, but regular installs of IPython from master will
>> definitely be broken while this is in-flight.
>>
>> -MinRK
>> ​
>>
>> _______________________________________________
>> IPython-dev mailing list
>> IPython-dev at scipy.org
>> http://mail.scipy.org/mailman/listinfo/ipython-dev
>>
>>
> _______________________________________________
> IPython-dev mailing list
> IPython-dev at scipy.org
> http://mail.scipy.org/mailman/listinfo/ipython-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/ipython-dev/attachments/20150324/4c73f282/attachment.html>