Hi,
Thanks for pointing this Andy! I think it would help indeed to set some
coarse deadline for the next release. This would help us get motion and get
things done. End of december or beginning of January would be best for me.
On my side, I don't plan to contribute anything big in the meantime.
However, I'd like to help and review on the following issues/PR :
- #2120: Multi-Layer Perceptron (this is mostly done, final round of
reviews on going on)
- #2570: Help Peter with improvements on the tree/gbrt modules
- #2285: MARS - It would really be too bad to let this PR die. We should
either help @jcrudy on this one or take the lead from there.
Should we head for shortly after NIPS? Maybe do a bit of merging and
> issue resolving there?
>
Sure, we could work at NIPS on some of the issues.
GIlles
------------------------------------------------------------------------------
November Webinars for C, C++, Fortran Developers
Accelerate application performance with scalable programming models. Explore
techniques for threading, error checking, porting, and tuning. Get the most
from the latest Intel processors and coprocessors. See abstracts and register
http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk
_______________________________________________
Scikit-learn-general mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/scikit-learn-general
