Hi Christian,

>>In case that the changed functionality/behaviour is controversial, this
>>should be discussed in the project and if needed, escalated to the
>>project lead (next step of escalation would be project leads list).
> 
> We already saw how good that works :-/ (the page-format in "File"-menu issue,
> plugin and applets in impress as two examples :-(()

I agree that there is an open issue here. I'm probably even on your side
to a certain extent (hey, I fought this quickstarter change, and a few
others from this category, myself :). But this is not in the scope of
the current discussion. Thus, I'd like to keep it out here, sorry.

However, I'd still like to include a statement about escalation, as this
is an important thing for users. Whether and how this works is another
story, though.

> This is sill workarounding lack of features in IssueZilla. Other
> bugtrackers have both severity and priority. We only have one. And that
> is not really used "properly" - but mainly as an "excuse" to not fix or
> look at "low-priority" issues.

(Other bug trackers also have a "blocking release XY flag", which can be
requested, approved, and denied. If we had those, the whole discussion
here were obsolete.)

> But better than nothing. 

Yes.

>>  release_blocker:
>>    This keyword denotes issues which describe a regression, i.e.
>>    functionality which worked in an older version, but is broken in a
>>    newer version. In opposite to the "regression" keyword,
>>    "release_blocker" marks issues which are considered a blocker for
>>    the next maintanance release.
> 
> 
> So does this *only* apply to regressions or to other issues as well?

I think there meanwhile is a consensus here that this should not be
about regression issues only.

> And who decides whether it is a "release_blocker" or a regular
> regression? - Often enough opinions differ.

Who decides this today?

That is: I don't know, and I am pretty sure I don't want to embark on
this for the moment. Again, this is a controversial topic, but it is
independent from the (technicaly) question whether we want to mark
blockers by target or by keyword. So, I would again like to ask you to
separate this question, sorry.

Ciao
Frank

-- 
- Frank Schönheit, Software Engineer         [EMAIL PROTECTED] -
- Sun Microsystems                      http://www.sun.com/staroffice -
- OpenOffice.org Database                   http://dba.openoffice.org -
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to