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?
- Below added by Jeremiah --
Acceptance criteria (AC) for closing this issue: Clear determination of when a PureOS issue should be marked as "resolved"