| Re: [mdt-papyrus.dev] Governance - SysML 1.1 editors - semantics of ASSIGNED |
|
Hi, Klaas, Christian In short :
Having a bug assigned to project Inbox means nothing (I guess it’s only done to send automatic emails to registered users) My 2 cents : It seems to me that when a bug is created it is automatically assigned to Project Inbox (Check the newly created bug [1]) Here is the process I follow for
[SysML 1.4] bugs :
-
Try to reproduce the bug
-
If reproduced pass the Bug Status from UNCONFIRMED To NEW
-
When someone works on it the set the Assigned To
-
When someone is identified for the (Gerrit) review set the QA Contact
-
When the gerrit patch is merged pass the Bug Status to CLOSE FIXED I believe that it is the standard workflow for Bugzilla (Except that I should probably use Fixed after the merge and move everything to close after the release & release note
publication) For SysML 1.1:
-
I try to add [SysML 1.1] in the title when the bug isn’t present in SysML 1.4
-
For me, these bugs could be pass to CLOSE WON’T FIX when SysML 1.1 will be removed from the release train
-
In the meantime : No idea Regards, Benoit 1 :
https://bugs.eclipse.org/bugs/show_bug.cgi?id=483401 De : mdt-papyrus.dev-bounces@xxxxxxxxxxx [mailto:mdt-papyrus.dev-bounces@xxxxxxxxxxx]
De la part de Christian W. Damus Hi, Klaas, I have the same understanding as you about the meaning of assigned state, when the assignee is an identifiable committer/contributor. When the assignee is the inbox, that is the Papyrus team’s way of indicating that the triage process
has confirmed the validity of a bug without actually assigning it to a specific person and milestone. For myself, I try always to set the assigned state, myself as the assignee, and a specific target milestone when I actually schedule work on a bug. It doesn’t mean that I’m starting to work on it, just that I am committing (as much as
that is realistic) to completing it by that milestone. A question for the team: is it general practice to assign bugs to oneself before working on them? I often see bugs resolved that are still assigned to the inbox. And do we consistently use the target
milestone field? So, anyways, I don’t know whether it’s feasible for you to filter bugzilla queries to exclude assigned bugs that don’t have target milestones and/or are assigned to the inbox, because I would expect that many of those would actually be
“in play” for this release. Cheers, Christian On Fri, Nov 27, 2015 at 11:40 AM, Klaas Gadeyne <Klaas.Gadeyne@xxxxxxxxxxxxxxx> wrote:
|