On Tue, Feb 26, 2013 at 5:43 PM, Ondřej Čertík <ondrej.cer...@gmail.com>wrote:
> On Tue, Feb 26, 2013 at 1:21 PM, Charles R Harris > <charlesr.har...@gmail.com> wrote: > > > > > > On Tue, Feb 26, 2013 at 2:03 PM, Ralf Gommers <ralf.gomm...@gmail.com> > > wrote: > >> > >> > >> > >> > >> On Tue, Feb 26, 2013 at 7:47 PM, Charles R Harris > >> <charlesr.har...@gmail.com> wrote: > >>> > >>> When should we put out 1.7.1? Discuss ;) > >> > >> > >> When we have X times more fixes in maintenance/1.7.x than the one commit > >> with a one-liner fix that we have now. Where X is >= 5 at least, unless > >> there's a very high prio fix that needs releasing asap? > >> > >> Having at least 2 months between bugfix releases unless something very > >> urgent comes up would also make sense to me. > >> > >> I think we do need to be diligent in backporting fixes quickly after > >> they're merged into master, and not leaving that till right before the > >> release candidate is scheduled. > >> > > > > Ralph, the backports are PR's marked with the backport tag and there are > > more than one. It is up to Ondrej to decide whether to include them or > not. > > I can't see the backport tag. How can I find it at github? > > Otherwise I think we should release sooner, I think this bug is quite > annoying > for scikit-learn: > > https://github.com/scikit-learn/scikit-learn/issues/1715 > > I don't know the best way, but you can go to the search box, type numpy/numpy issues, and when the results come up select the stable 1.7 backport milestone. Nathaniel committed a bunch, but it looks like there is still one to backport. Chuck
_______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion