On 06/05/2014 03:24 PM, Olivier Grisel wrote: > I don't think this is possible and this is not what we did for > previous releases: > > For instance: > > The release 0.13 is in branch 0.13.X but not master: > https://github.com/scikit-learn/scikit-learn/commit/9cf67f961e3d0b493f432df0201d91bd0a7dcedf > > The release 0.14(.0) is in branch 0.14.X but not master: > https://github.com/scikit-learn/scikit-learn/commit/d13928cc0653f52de55e22118915b0c5bcba13d7 > > The release 0.14.1 is in branch 0.14.X but not master: > https://github.com/scikit-learn/scikit-learn/commit/34c4908369968dd0f77897ec9dd8c227e7545478 > > > I think we should stick to that scheme. >
Wait, they should be in master, right? Well we need to change the version is master, too. I think I did some cherry picking because that seemed easier at the time, but maybe just merging the release in master would be the right thing to do. I'm not sure why I did the release the way I did back then.... maybe because it is an unneccessary commit, be cause the version is then changed again? ------------------------------------------------------------------------------ Learn Graph Databases - Download FREE O'Reilly Book "Graph Databases" is the definitive new guide to graph databases and their applications. Written by three acclaimed leaders in the field, this first edition is now available. Download your free book today! http://p.sf.net/sfu/NeoTech _______________________________________________ Scikit-learn-general mailing list Scikit-learn-general@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/scikit-learn-general
