> > In mid-september there will be a scikit-learn sprint in Paris: > http://www.pycon.fr/2012/ but we don't need to wait for that sprint > to > make a new release. > I think releasing before that makes more sense. Usually sprints create lots of PRs that need to be reviewed.
> I don't want to push any particular feature / fix for that release > (or > any other release BTW). I think it's best to release what has been > merged to master every 3-4 months and let the regular review work > happen without any time pressure. > Good point. Btw, my long-term goal is sklearn 1.0, which to me means fast, stable, well-documented functions with a consistent interface. Therefore I like to focus on what we have and make that better. Except for the SGD module, that's just to cool ;) ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Scikit-learn-general mailing list Scikit-learn-general@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/scikit-learn-general
