Re: Should we do an IPython 4.1 soon ?

MinRK <[email protected]>
Newsgroups gmane.comp.python.ipython.devel
Message-ID <CAHNn8BVDVLvem6wMYOb2C1S4G7dP4_CYteHrGqfr+Tx1GWpxDQ@mail.gmail.com>
Given the resources involved in getting notebook-4.1 out the door, I think
we should probably focus on that and wait on starting the IPython release
process until notebook-4.1 ships, but I think we can start IPython 4.1
immediately after we ship the notebook release. I think IPython's in a
pretty releasable state right now, so it shouldn't take long to ship
IPython 4.1.

-MinRK

On Mon, Dec 14, 2015 at 12:58 PM, Matthias Bussonnier <
[email protected]> wrote:

> Hi all,
>
> With the separation of the multiple project, as of The Big Split,
> the pace on IPython terminal itself has been much slower than usual, with
> relatively low number of new features, but still a few bug fixes and
> improvement
> here and there that users are waiting for.
>
> For example no PR merged in 13 days as of this writing, and nothing
> especially important for 4.1.
>
> I propose that we release a 4.1 mostly bug fix soon (monthish ? Earlier
> ?), and try to keep now a relatively
> slow moving, regular minor release for the 4.x branch, like one minor
> release every 8 weeks.
> I’ve already put a 4.1 release for mid January in GitHub, and 4.2 2 month
> after that.
>
> I think a regular release schedule would be welcomed for us (we tend to
> live of master and forget that end user
> experience bugs) and for end user to know what to expect.
>
> That would likely mean that any API breakage PR would be targeted as 5.0
> branch.
>
> Thoughts  ?
> --
> M
>
> _______________________________________________
> IPython-dev mailing list
> [email protected]
> https://mail.scipy.org/mailman/listinfo/ipython-dev
>

_______________________________________________
IPython-dev mailing list
[email protected]
https://mail.scipy.org/mailman/listinfo/ipython-dev
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.