Christian Lohmaier wrote:
On Thu, Jun 02, 2005 at 03:54:31PM +0200, Joerg Barfurth wrote:
Christian Lohmaier wrote:
issues that won't be dealt with by Sun because of workload, bad
effort/gain ratio, of no interest because StarOffice has commercial
replacement, ... ("We won't implement it, but just go ahead and povide a
patch") should not be closed wontfix but "worksforme" with TM
"OOoPleaseHelp" (unless there is a dedicated resolution for this kind of
stuff)
I don't agree that they should be closed. An issue that is closed to me
is gone. I would exclude it from any queries, except post-mortem
statistical evaluations.
That is exactly the idea behind closing it. Get it out of the way, leave
the issues that are being worked on/that have not yet been decided upon.
There are many different roles in this project, which do different
things with existing issues. Some examples
1. Look for existing issues
a) before submitting an own one
b) during evaluation
2. Confirm, evaluate and dispatch new issues
3. Look for issues to implement
a) during release planning
b) as independent developer
4. Plan and track your development work
5. Track the feature status/quality of releases in progress
In this selection each task has a different set of issues with which to
work.
The issues we are talking about are not at all relevant only for 2. and
4. They are very relevant for both 1. and 3b). These two tasks are often
done by newcomers with limited experience in dealing with issuezilla.
Thus our issues really should not be closed and should even be included
in the default queries.
If you regularly do activities like 2. and 4. you probably will set up
saved queries adapted to your needs anyhow - so excluding issues having
the 'OOo PleaseHelp' target or marked RESOLVED/LATER would be trivial.
Otherwise you can still easily adopt the habit to deselect it every time.
It might be assigned to a dummy owner and/or we might use the useless
RESOLVED-LATER status for it, but we should not close it.
I disagree, mainly because of working on the open issues gets easier
when the issues that nobody's working on are not in the way.
If a developer looks for issues he could take on, he will look at things
that are still open, rather than closed (i.e. dealt with for good).
If you don't close them, you'll have to exclude the target OOoPleaseHelp
in every query again and again..
It depends on the goals of your query. And yes, the initial query
defaults in issuezilla will not suit every role.
The most important characteristic of such an issue is that
- it is OPEN
- it has target milestone OOoPleaseHelp
My opinion is: Open issues are those that some action is going to be
taken.
Open issues are those on which some action may be taken. Closed issues
are those on which no action will be taken any more. If you have a
current issue that looks duplicate to a closed issue you should
generally submit a new one. The closed one is done.
To me it doesn't make sense to have issues open that nobody
is/will be working on. Leaving it open may signal to the reporter that
the issue is handled.
Closing it makes clear that unless someone
interested takes care of the issue, it will never see the light of day.
'resolving' as LATER (or something similar) or leaving as NEW and
setting a 'target' of 'PleaseHelp' should be clear indications that the
issue is not being handled currently and that it probably won't be done
unless someone jumps in.
BTW: I've seen cases where such issues were fixed by the responsible
developer after all when working on the relevant section of the code or
were taken into account when a related feature was specified, because
the requested change was no extra effort. For this to occur, it is
useful to keep it in sight of the developer. And if the issue was
already closed, you'd never notice that. As priorities and goals change,
such issues may even be taken over actively by Sun developers after a while.
Closing it with an appropriate comment may even result in the reporter
searching for "independent" developers actively while such "pressure" is
not createn by leaving the issue open and letting it rot...
It shouldn't rot without comment or target. But target milestone and
status are the correct fields to express the state of a non-resolved issue.
Ciao, J�rg
--
Joerg Barfurth Sun Microsystems - Desktop - Hamburg
>>>>>>>>>>>>>>>>>> using std::disclaimer <<<<<<<<<<<<<<<<<<<<<<<
Software Engineer [EMAIL PROTECTED]
OpenOffice.org Configuration http://util.openoffice.org
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
