[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
[mdt-papyrus.dev] Governance - SysML 1.1 editors - semantics of ASSIGNED
|
Hi Papyrus developers,
(This email focuses on the SysML 1.1 editors, although the question might
be considered more general)
As mentioned in Bug 427378, I noticed that there are quite a (whole) lot
of SysML 1.1 bugs in the ASSIGNED state (and have been in that state for
ages). I¹m not sure what the (agreed) meaning of assigned is in the
papyrus project, but to the end user it is currently _very_ unclear if
anything is going to happen to a bug in the ASSIGNED state. [*]
My personal definition of ASSIGNED would be that work is going to start on
that bug in a to-be-defined-but-fixed period starting from the moment the
bug is in the assigned state.
For instance, my _impression_ is that nothing is going to happen to (all)
the (non-critical) SysML 1.1 bugs unless somebody stands up and says
he/she wants to fund them, right?
Wouldn't it be more honest/realistic to either put these bugs in a
NEW/CONFIRMED state (or close these bug as CLOSED WONTFIX)?
BR,
Klaas
[*] This would for instance also allow to clearly answer (the tons of)
forum posts questions such as
https://www.eclipse.org/forums/index.php/t/1070659/
