[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [mdt-papyrus.dev] closing old bugs
|
Hi Christian, Thanks for your feedback, you are asking the right questions. I am really answering directly to your question. Nevertheless here some additional elements To my point of view as we are migrating to new major version (thanks a lot for you email on the API), we could also take time to improve our Bugzilla workflow. To my point of view, I would like we follow the Eclipse convention. The QA could be in charge to switch from fixed to verified the bug. I have found in the Eclipse documentation that “When the project does a major release, the VERIFIED bugs are changed to CLOSED.” Francois [1]: https://wiki.eclipse.org/Development_Resources/HOWTO/Bugzilla_Use De : mdt-papyrus.dev-bounces@xxxxxxxxxxx [mailto:mdt-papyrus.dev-bounces@xxxxxxxxxxx] De la part de Christian W. Damus Envoyé : lundi 25 janvier 2016 15:04 À : Papyrus Project list <mdt-papyrus.dev@xxxxxxxxxxx> Objet : Re: [mdt-papyrus.dev] closing old bugs Hi, When I run bugzilla reports, I lump all resolved, verified, and closed bugs together as logically “completed” because (correct me if I’m wrong) Papyrus doesn’t have a formal QA process in which a QA team tests resolved bugs to move them into verified state (or reopen them [1]), after which the original reporter can close them if in agreement with the verification results. Some projects in the Eclipse Modeling family actually use the verified state to indicate that fixes for bugs that were in the resolved state have actually been published to the update site. This transition was at one time automated by the builds. So, I guess my question is what precisely do we think would be the value (for Papyrus) of following bugs through a process beyond the resolved state? What meaning do we want to assign to verified (if any) and closed states to distinguish them from resolved? And who is responsible for transitions through these states? Cheers, Christian
[1]: Note that the very transition from resolved -> reopened implies a “closedness” of the resolved state. |
Attachment:
smime.p7s
Description: S/MIME cryptographic signature