On Tue, 2012-11-27 at 22:23 +0000, Tim Landscheidt wrote: > If at the moment the priority field neither necessarily > triggers action nor reflects the actual state of affairs, > why even bother and not just delete/hide it from view? This > would free more time to fix bugs.
I don't see how dropping it all together helps planning or how it "frees more time". Obviously anybody is free to work on anything but some stuff simply is more important than other stuff. I understand that there are many options and ways to express that importance though, and that "severity", "priority", "target milestones", "blocker bugs" have some ambiguity to discuss in the long run. Right now I'd like to introduce a clear way to mark issues that should be handled immediately. > Not to quote from another video about GitHub (where "issues" > have only title and comment), let's not forget Git: No bug- > tracker at all :-). I'm happy if using http://dir.gmane.org/gmane.comp.version-control.git works well for the Git developers and if important issues don't get lost. There are many ways and tools how to do software development, some work well for some, others work well for others, and not every tool is needed by everybody. GitHub itself has a bugtracker ("Issues" tab) by the way. andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ _______________________________________________ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
