Bug 23155

Summary: Tidy up Bugzilla statuses
Product: Project Infrastructure Reporter: Martin Renvoize (ashimema) <martin.renvoize>
Component: BugzillaAssignee: Jonathan Druart <jonathan.druart>
Status: CLOSED FIXED QA Contact:
Severity: trivial    
Priority: P5 - low    
Version: unspecified   
Hardware: All   
OS: All   
GIT URL: Change sponsored?: ---
Patch complexity: --- Documentation contact:
Documentation submission: Text to go in the release notes:
Version(s) released in:
Circulation function:

Description Martin Renvoize (ashimema) 2019-06-19 10:21:49 UTC
We've discussed this at a couple of dev meetings now, and I've raised it again to ensure a consensus at the next meeting..

It would be nice to clear up some of our superflous status's and clarify a few of those in use.

My proposal was:

* Add 'Pushed to oldstable'
* Add 'Pushed to oldoldstable'
* Remove 'Pushed for QA'
* Remove 'Pushed by Module Maintainer'
Comment 1 Jonathan Druart 2019-06-19 15:13:19 UTC
What happens on release time, when oldstable become oldoldstable?
Actually when pushed to oldoldstable should not it be RESOLVED FIXED?
Comment 2 Martin Renvoize (ashimema) 2019-06-20 15:09:22 UTC
My proposal way back when was for rmaints to set 'Pushed to ...' for each of their respective branches as they push.. and then for the release tools to include a change to 'RESOLVED FIXED' on mass at release time.

I even have the scripts to do this all built, but the caveat there is that doing any sort of bulk action like that triggers a metric tonne of emails and hence the idea went on hold somewhat..

Happy to be guided.
Comment 3 Katrin Fischer 2023-10-08 10:57:17 UTC
> 
> My proposal was:
> 
> * Add 'Pushed to oldstable'
> * Add 'Pushed to oldoldstable'
> * Remove 'Pushed for QA'
> * Remove 'Pushed by Module Maintainer'

I believe this has been done - please re-open if I missed something!