[Foresight-devel] How we deal with issues in JIRA

[Thilo Pfennig]

I suggest that we do not change the focus of a bug report. But rather
declare it as fixed and open a new bug for things that keep to be
unresolved. if you look at this bug:

"Cannot switch to a differente keyboard layout via the gnome applet"
http://issues.foresightlinux.org/browse/FL-27

The real bug was that you could not switch keyboard layout. This was fixed.

the bug now rather is that this gnome applet is not working without a cras
which is a totally different issue in my view. Its not a visible bug because
the applet is not there. The new bug reall should have the topic like
"adding the applet to the panel causes gnome-settings-daemon to crash."

If we dont close bugs more sooner my guess is that we will not be able to
close many bugs at all, because every package is never 100% perfect. Also
people will not be able to recognize the issue and likely will file new
issues with better names. Thena we get more duplicates.

I would vote for smaller bugs that get fixed and we can move on and also get
bugs fixed. An issue should at beste describe gthe exact problem and should
be closed if the core problem is solved.

If developers like to keep an issue open this should be because they are
currently working on fixing it up. I dont like long standing issues that are
not described accurately and nobody works on. We could also say that
removing the applet is some kind of fix. And that the real issue would be
somebody wanting this applet.

So I would tend to rather close an issue like this. The thing is also that
we do update frequently and maybe this applet does not crash anything. Then
its also more a matter of packaging. I would suggest that such measures to
remove a component out of a trove are commented with a link to an issue or
similar, so that other packagers can try to recook and remove the disabling
od a feature if it works. Its sometimes hard to actually see why some things
where patched, added or removed.


Thilo



-- 
Thilo Pfennig
http://issues.foresightlinux.org/confluence/x/R