[IPython-dev] We might actually make 0.13 by June 30, jump in to make it possible!
Tue Jun 26 16:52:32 CDT 2012
Can we get a new flag for the issue tracker that indicates that it's
expected to be an issue you can go at without knowing much IPython voodoo?
I'm happy to knock out some copy for the site if I can get something to
On Jun 26, 2012 6:55 AM, "Fernando Perez" <firstname.lastname@example.org> wrote:
> Hi all,
> the 0.13 milestone board is actually looking pretty solid (after some
> aggressive triage and new code today):
> We have 7 open PRs and 5 issues, 4 of which are closed by a PR. The
> remaining issue, #1702, has a pending discussion on what we should do
> with it given there's no code ready to close it.
> So I think that if people can jump in with testing and review on any
> of these that you can help with, and we get the release notes in
> shape, we can actually do the release quite quickly.
> Our CI bots on Shining Panda and Travis are looking solid:
> On SP we cover python 2.6, 2.7, 3.1, 3.2 and 3.3, and Linux, Mac and
> Windows, though not all OSes cover all python versions, so I think
> it's not unreasonable to move forward with the release once we merge
> the PRs we have open.
> So please jump in if you can help, esp. with the release notes/website
> work, so we can cut this quickly and open again for development.
> Thanks to everyone for all the great recent contributions, and a
> special one to Thomas Kluyver and Marc Abramowitz for the Shining
> Panda and Travis-CI setup. The value of CI becomes particularly clear
> near release time, as I feel much more confident moving forward
> without having to wait for weeks of RCs going out to people for manual
> IPython-dev mailing list
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the IPython-dev