I agree, but for this specific issue, I thought that the consensus was 'give a
warning' and so now it should be fairly clear what to do. I tried to avoid
tagging issues as easy if high level knowledge was needed, maybe I didn't
succeed.
Andy
--
Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.
Robert Layton <[email protected]> schrieb:
On 2 September 2012 23:26, Andreas Mueller <[email protected]> wrote:
Done.
A little different now, though.
73 Cleanup / Enhancement 30 Crash / Bug 9 Documentation 17 Easy 11
Moderate 80 New Feature I found it hard to distinguish Cleanup and API stuff,
so I just merge the two.
Now all issues / PRs have either a Crash, Cleanup, Documentation or New Feature
tag.
That gives a nice traffic light feel to the importance of the issue.
Apart from "Easy" for newcommers, I also introduced a "Moderate" for
non-core-devs. The idea was to have the "easy" really easy.
If I misjudged anywhere, feel free to retag.
I hope this benefits the development process.
Docs coming soon.
Cheers,
Andy
On 09/02/2012 02:10 PM, Andreas Mueller wrote:
Hey everybody. I noticed in the last couple of month that the way we use tags
on the issues makes them pretty useless. At least they are useless to me and I
am working on the issues quite often. The only thing that I found helpful is
the "easy fix" tag, but not everything that was "easy fix" really was one. I
suggest to remove all tags as they are currently used and establish a new
system, with the following tags: - bug: something that clearly shouldn't
happen. There are some of those hidden on the issue list beneath 100 feature
requests. - easy fix: something that a newcomer could tackle. - cleanup/enh:
issues where the code is ugly and/or slow - feature request: something that is
not there, but you want to have. It's absent is not a bug though. - api:
inconsistent api problems - documentation: places where the documentation is
wrong or below standards. This directly gives them some sort of hierarchy. The
bugs are clearly more important to fix than the feature requests. At t
he
moment, when I am looking for bugs to fix, or see if a bug is known, I have to
dig through 200 issues. WDYT? btw: I volunteer to retag all issues. Andy
------------------------------------------------------------------------------
Live Security Virtual Conference Exclusive live event will cover all the ways
today's security and threat landscape has changed and how IT managers can
respond. Discussions will include endpoint security, mobile security and the
latest in malware threats.
http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________ Scikit-learn-general mailing
list [email protected]
https://lists.sourceforge.net/lists/listinfo/scikit-learn-general
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Scikit-learn-general mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/scikit-learn-general
I find occasionally that some of the "easy" fixes are easy technically, but
require deep thought and specific "high-level" decisions to be made, such as
#989: Raise warning if only one class presented to classifier.
Once a decision has been made on what to do, then this is a very easy fix.
Still, I wouldn't call this "bug" easy though.
Given that we generally direct newcomers to check out the easy bugs first, we
should probably differentiate between "needs decision, but otherwise easy" and
"easy and ready to do".
- Robert
--
Public key at: http://pgp.mit.edu/ Search for this email address and select the
key from "2011-08-19" (key id: 54BA8735)
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Scikit-learn-general mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/scikit-learn-general
