We could start with assigning priority labels like they use in numpy... That + milestones could help us prioritize?
On Sat, Dec 3, 2016 at 11:52 AM, Gael Varoquaux < gael.varoqu...@normalesup.org> wrote: > On Fri, Dec 02, 2016 at 07:52:09PM -0500, Andy wrote: > > So did we ever decide on how to prioritize reviews? > > I don't know how to do this. > > > I think it might be helpful if Joel and me prioritize issues. > > I think that it would be useful. Although of course different people will > have different priorities (depending for instance on the type of data > that we process). I guess that we can agree on a large part of the > prioritization, and hence it will be useful. > > > Obviously that will only make sense if the other team members check up > > on it when deciding what to review / work on. > > So, the big question is: how do we do this? Isn't there on of the many > project-management extension of github that enables this? > _______________________________________________ > scikit-learn mailing list > scikit-learn@python.org > https://mail.python.org/mailman/listinfo/scikit-learn > -- Raghav RV https://github.com/raghavrv
_______________________________________________ scikit-learn mailing list scikit-learn@python.org https://mail.python.org/mailman/listinfo/scikit-learn
