Thread: "Fixed in Fremantle"
View Single Post
Andre Klapper's Avatar
Andre Klapper is offline Andre Klapper
2008-12-01 , 11:43
Posts: 1,665 | Thanked: 1,649 times | Joined on Jun 2008 @ Praha, Czech Republic
#105
Why do such discussion always rise when I'm completely offline for a long weekend?
From a quick readthrough, most things have been explained already in this thread. Just picking up a small issue:

Originally Posted by Jaffa View Post
To be fair, this has only relatively recently been decided, and if there's consensus on an even better process, nothing should stop it from being adopted.
Correct. That's what we also have the wiki for... I've now described the current situation of RESOLVED FIXED state at https://wiki.maemo.org/Bugsquad and of course it's open for discussion to improve, e.g. here or on the maemo-community mailing list (the latter I will definitely not miss).

Originally Posted by Jaffa View Post
Perhaps a modification of the "target" milestone would help. Ideally, of course, the issue would be assigned to the appropriate designer/developer/reviewer/architect to act as a master for the development. It would then be updated with specs and assigned through the development workflow, finally being FIXED when the code is committed to some repository somewhere (hopefully a publicly visible one).
I assume you only refer to enhancement requests here?

Originally Posted by Jaffa View Post
Failing that, what about keeping them open and assigned to "fremantle@maemo.bugs", again until some (internal) build of the software meets the requirement as outlined.
At least for bugs I'd say: Basically because it adds noise if keeping them in open state. Querying for bugs in FIXED state and with Target Milestone == Fremantle set shows up those bugs and removes the noise when taking a look at open requests that still need to be handled.
__________________
maemo.org Bugmaster
 

The Following 2 Users Say Thank You to Andre Klapper For This Useful Post: