Re: [sage-devel] Re: Trac field priority
On 2014-11-05 20:10, kcrisman wrote: No documentation other than various email assertions about blockers being true blockers (see the thread you forwarded this from for an example!). The real question is major to whom? But that is not easy to answer, other than on obvious things like Sage doesn't start on popular platform X but did last week. I would say: * blocker = either stuff which really prevents people from using Sage (e.g. OS X 10.10 port) or important regressions (i.e. stuff which worked in the last released version but no longer works). * critical = serious mathematical mistakes or crashes in basic Sage functionality * major (default) = when in doubt, use this * minor/trivial = less important things like documentation bugs... In practice, only the blocker priority really matters. Note that priority has nothing to do with the deepness or complexity of the issue, I often create blocker tickets with trivial fixes. -- You received this message because you are subscribed to the Google Groups sage-devel group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
[sage-devel] Re: Trac field priority
On Wed, 5 Nov 2014, kcrisman wrote: How DOES bug prioritization work in Sage? You can pick blocker/critical/major/minor/trivial when you're creating a ticket. - -There is certainly very little double-checking, and very little setting to anything other than major: Is there even documentation about using trac fields? How should one differentiate between major and minor? -- Jori Mäntysalo -- You received this message because you are subscribed to the Google Groups sage-devel group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
[sage-devel] Re: Trac field priority
How DOES bug prioritization work in Sage? You can pick blocker/critical/major/minor/trivial when you're creating a ticket. - -There is certainly very little double-checking, and very little setting to anything other than major: Is there even documentation about using trac fields? How should one differentiate between major and minor? No documentation other than various email assertions about blockers being true blockers (see the thread you forwarded this from for an example!). The real question is major to whom? But that is not easy to answer, other than on obvious things like Sage doesn't start on popular platform X but did last week. (And to be sure, too much documentation about this will probably become a roadblock to people actually reporting stuff, because they have to agonize over the priority.) -- You received this message because you are subscribed to the Google Groups sage-devel group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
