As usual, I agree ;)
I think it would be good to call out particularly important bugfixes so
they get reviews.
We might also want to think about how we can organize the issue tracker
better.
Having more full-time people on the project certainly means more
activity but ideally we can use some of that time to make the issue
tracker more organized.
On 8/5/19 9:21 AM, Joel Nothman wrote:
Yay for technology! Awesome to see you all and have some matters
clarified.
Adrin is right that the issue tracker is increasingly overwhelming
(because there are more awesome people hired to work on the project,
more frequent sprints, etc). This meeting is a useful summary.
The meeting mostly focussed on big features. We should be careful to
not leave behind important bugs fixes and work originating outside the
core devs.
Despite that: Some of Guillaume's activities got cut off. I think it
would be great to progress both on stacking and resampling before the
next release.
I also think these meetings should, as a standing item, note the
estimated upcoming release schedule, to help us remain aware of that
cadence.
Good night!
J
_______________________________________________
scikit-learn mailing list
scikit-learn@python.org
https://mail.python.org/mailman/listinfo/scikit-learn
_______________________________________________
scikit-learn mailing list
scikit-learn@python.org
https://mail.python.org/mailman/listinfo/scikit-learn
