[SciPy-Dev] 0.16.0 release

[Ralf Gommers]

On Tue, Apr 28, 2015 at 12:01 AM, Evgeni Burovski <
evgeny.burovskiy at gmail.com> wrote:

> On Sun, Apr 26, 2015 at 3:22 PM, Ralf Gommers <ralf.gommers at gmail.com>
> wrote:
> >
> >
> > On Sun, Apr 5, 2015 at 9:40 PM, Ralf Gommers <ralf.gommers at gmail.com>
> wrote:
> >>
> >> Hi Abraham, Andreas,
> >>
> >> Thanks for your interest to both of you!
> >>
> >> The release manager is the person that is responsible for a number of
> >> actions to get from "now we start planning for the next release" to
> "this
> >> release is done". This description should give a reasonable overview
> (some
> >> details may be a bit outdated):
> >> https://github.com/numpy/numpy/blob/master/doc/HOWTO_RELEASE.rst.txt
> >>
> >> The release manager is the person that has the final responsibility for
> >> what does and does not go into a release, what are considered blocking
> >> issues, etc. This part really has to be done by a core developer.
> However,
> >> there's a lot of other things that the release manager also usually
> takes
> >> care of which could equally well be done by one or more contributors
> who are
> >> not core developers. Here's a list:
> >> - build/test Windows and OS X binaries (.exe, .dmg, .whl)
> >> - automate those binary builds/tests further
> >> - tackle some of the issues that need to be resolved before the alpha /
> >> beta / final release
> >> - PRs to complete the release notes and contributor name mapping
> >> - a PR to the scipy.org repo to put the release in the News section
> >> - improve documentation of the release process itself (the less you know
> >> to start with, the better you can document it)
> >>
> >> Things that the release manager should do himself:
> >> - propose the release schedule (dates for alpha/beta/rc/final)
> >> - create the maintenance/0.16.x branch
> >> - tag the (pre-)releases
> >> - send the release announcement emails
> >> - upload binaries to PyPi and SourceForge
> >> - propose/make decisions on blockers and content
> >>
> >> And what's always a team effort: merge as many PRs as possible before
> the
> >> release split.
> >>
> >> I hope this gives a clear picture. A "release team" that jointly tackles
> >> the above tasks would be great. Still would like to see a core dev
> volunteer
> >> though:)
> >
> >
> > Okay, I'll volunteer to be the release manager for this release. Here's a
> > proposal for the release schedule:
> >
> > - branching 0.16.x: 10 May
> > - beta 1: 12 May
> > - release candidate 1: 24 May
> > - release candidate 2: 31 May (if needed)
> > - final release: 7 June
> >
> > There aren't many serious issues at the moment, the only nontrivial one
> is
> > the QR updating issue. Here's what's marked to go in still:
> > https://github.com/scipy/scipy/milestones/0.16.0. The above schedule
> gives
> > us two weeks to merge PRs. Of the larger ones, I'd still like to see
> these
> > go in:
> > - 4682: signal.csd/coherence/welch
> > - 4374: cKDTree rewrite
> >
> > If you see an issue that you consider a blocker or a PR that really
> should
> > go in, please label it with the 0.16.0 milestone or mention it here.
>
>
> permutation t-tests, https://github.com/scipy/scipy/pull/4440, look
> nearly ready (from a distance at least)
> A nice-to-have, not a release blocker for sure.
>

Indeed, would be nice to get that in. Added to the milestone for now.

Ralf



>
> Evgeni
>
>
> > Cheers,
> > Ralf
> >
> >
> >
> >>
> >>
> >> Cheers,
> >> Ralf
> >>
> >> P.S. I shouldn't forget to mention that for a long time Matthew Brett
> has
> >> been building the OS X wheels and done extensive Scipy Stack testing.
> And
> >> that for an even longer time Christoph Gohlke has been testing
> pre-releases
> >> with MSVC on Windows and resolving issues that are invariable found on
> that
> >> platform. I definitely consider them part of the "release team" (not
> that we
> >> have ever used that name before).
> >>
> >>
> >>
> >>
> >> On Sat, Apr 4, 2015 at 9:30 PM, Abraham Escalante <aeklant at gmail.com>
> >> wrote:
> >>>
> >>> Hi Ralf,
> >>>
> >>> This sounds interesting to me and I would like to contribute but I
> fear I
> >>> may be still too new to the community to be of much help but maybe I
> could
> >>> provide some assistance to learn.
> >>>
> >>> Is this a task for admins only? Is there a way I can contribute?
> >>>
> >>> Cheers,
> >>> Abraham.
> >>>
> >>> 2015-04-04 2:54 GMT-06:00 Ralf Gommers <ralf.gommers at gmail.com>:
> >>>>
> >>>> Hi all,
> >>>>
> >>>> It's about time to start preparing for the 0.16.0 release. Unusually,
> >>>> there are zero blocking issues it looks like. A lot of PRs to merge of
> >>>> course, but nothing very large that still needs a lot of work.
> >>>>
> >>>> Most important question: does anyone want to take the release manager
> >>>> role for this release? It would be good to start rotating this role
> for
> >>>> every minor release. This will help spread the knowledge on how to do
> >>>> releases and also spread the workload (it's not that much for a single
> >>>> release, but it adds up).
> >>>>
> >>>> Cheers,
> >>>> Ralf
> >>>>
> >>>>
> >>>> _______________________________________________
> >>>> SciPy-Dev mailing list
> >>>> SciPy-Dev at scipy.org
> >>>> http://mail.scipy.org/mailman/listinfo/scipy-dev
> >>>>
> >>>
> >>>
> >>> _______________________________________________
> >>> SciPy-Dev mailing list
> >>> SciPy-Dev at scipy.org
> >>> http://mail.scipy.org/mailman/listinfo/scipy-dev
> >>>
> >>
> >
> >
> > _______________________________________________
> > SciPy-Dev mailing list
> > SciPy-Dev at scipy.org
> > http://mail.scipy.org/mailman/listinfo/scipy-dev
> >
> _______________________________________________
> SciPy-Dev mailing list
> SciPy-Dev at scipy.org
> http://mail.scipy.org/mailman/listinfo/scipy-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/scipy-dev/attachments/20150428/f3fadbf2/attachment.html>