On Tuesday 14 January 2014 21:58:38 Tom Wijsman wrote: > On Sun, 05 Jan 2014 15:42:48 -0800 Brian Dolbec wrote: > > 2) start working on a solution, > > a) if you have significant progress, but need more time, mark it > > accordingly, assign it to yourself, leave a comment, etc. > > Assigning it to oneself is a quite good idea as it allows to easily keep > track of the bugs you are working on, otherwise you have to rely on > techniques that aren't optimal; which are unfortunate. > > In the lists of all bugs, that can be obtained by checking out the > product and/or categories; this gives a quite clear overview of who is > working on what, as well as which bugs are still free. As this is still > able to be done, there seems no need to assign the bug to Portage team.
i disagree. dev-portage@ get's cc-ed on bugs when they're being kept abreast of developments (like PMS), or someone just wants an opinion/feedback on an issue. so there's no way to differentiate between bugs that are assigned to the portage team and bugs where the portage team's opinion is being requested. i want a query for the former and i just rely on generated bugzilla e-mails for the latter. what's wrong with using the whiteboard ? it's a free text field and you can easily construct a query that produces exactly what you want. just stick in your username in there. > > 3) commit the fix. Mark it as InVCS, if not already, set status to > > IN_PROGRESS > > InVCS becomes redundant; other than that, good. i don't see how it's redundant. there is no other flag that indicates things have been fixed in the git tree and the only reason the bug remains open is that a release has not yet been cut. -mike
signature.asc
Description: This is a digitally signed message part.
