Sure, as you said there are lot of always-subjective variables involved, so much that the time to explain and then justify and talk about them is so long that, in the same lapse, we can fix around 40 opened issues. I don't like to talk about taste and "fried air", instead I prefer effective fixes/fix-proposals.
On Mon, Jul 18, 2011 at 12:22 PM, Ramon Smits <[email protected]> wrote: > My priority is Maddalena and Leticia... btw if we have to accept "my >> issues are more important for me than all other bugs because these are the >> bugs that affect me. That's just how it works." >> you may accept that, for us, your issues are not so important for the >> project... and that's just how it works. >> >> > Fabio (and others), > > He mentions and asks what the criteria for a priority are. I think that he > has e very good point as it is not really obvious. > > He says that currently there is a relation defined between a breaking issue > and having a high priority while this is not the way issues are solved. I > think it is important that this relation is not there and that the priority > is choosen by the core developers and with that a reason for the given > priority. This would make a lot of choices very transparent as there are a > lot of reasons for choosing a priority which is a mix of complexity, > affected userbase, change impact, testability and probably 10 more which all > *could* be valid arguments in priority weight. > > I completely under your response but that is not the only subject of this > thread. > > -- > Ramon > > > > > > -- Fabio Maulo
