Comment 18 for bug 1394731
Revision history for this message
| Didier Roche-Tolomelli (didrocks) wrote | #18 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
On another note, it will be great that every archive admin members follow the same procedure when promoting a package to main. The bug is still opened and not fixed release, I was not even aware then that it's been promoted already. I don't think I handle that promotion on the 04 of march, which is quite recent (my logs and command doesn't show this). Sad that we don't have in the UI launchpad logs showing who originated the request.
What I personally do when promoting a package is that I tend to copy/paste the promote command output on the bug itself when changing the status. That's also a way to ensure the archive admin checked that a MIR was filled if needed. (I also always separate the "Fix committed/Fix released" in 2 separates steps when I'm handling both in one run). Can we move the archive admin process around this?