| 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. On 25 January, 2016 at 08:37:39, LE FEVRE FRANCOIS (francois.le-fevre@xxxxxx) wrote:
|