unspecified when a PureOS issue is truly "resolved"
Open, Needs TriagePublic

Description

We track issues for PureOS, and when the issue is resolved we flag it as such.

Typically we flag issues as solved as soon as fix has "landed" - i.e. a) is applied to a package and released to the "landing" suite.
Our users - and colleagues testing - will however continue to experience, and ideally report as broken, until an issue b) has entered "green" suite, or for parts of the default set until c) inclusion in newest installer image.

Which is it? And if answer is "all of them" then how do we uniformly handle that with this issue tracker?

Suggestion - can we figure out a workflow with subtasks and/or parent tasks? That way there's no need to look outside of this issue tracker for solutions, and we can sort/clean up current tasks here that may be in the kind of limbo you describe.

Add Comment