On 12/03/2016 01:20 PM, Nelle Varoquaux wrote:
On 3 December 2016 at 10:08, Andy <t3k...@gmail.com> wrote:
On 12/03/2016 12:26 PM, Raghav R V wrote:
We could start with assigning priority labels like they use in numpy...
That + milestones could help us prioritize?
I feel milestones are too coarse. Or I'm using them wrong.
And priority labels only work if people don't use the "high priority" all
the time.
There is a lot of stuff labeled "bug", which I would interpret as "highest
priority" that people don't look at at all.
even milestone only work if people don't use the next milestone all
the time. I think the only milestone useful is for release critical
bugs, for the next release.
For example, on matplotlib, I am currently only reviewing and working
on tickets for the 2.0 milestone, as we're hoping to get a new
candidate release out this week-end.
That's what I meant by "probably doing it wrong".
I assign it to too often.
But actually I think people mostly ignore it anyhow ;)
_______________________________________________
scikit-learn mailing list
scikit-learn@python.org
https://mail.python.org/mailman/listinfo/scikit-learn
