| Summary: | Need Milestones 5.0 M1-M4, 5.1 | ||
|---|---|---|---|
| Product: | [Infrastructure] Bugzilla | Reporter: | Stephen K Jolley <sjolley.yp.pm> |
| Component: | bugzilla | Assignee: | Michael Halstead <mhalstead> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Medium+ | CC: | infras.bug.watcher, Infras.watcher, randy.macleod, richard.purdie, steve |
| Version: | unspecified | ||
| Target Milestone: | Q3 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |
|
Description
Stephen K Jolley
2023-08-31 14:58:31 UTC
Changing all bugs from 4.4 to 5.0 and all bugs from 4.99 to 5.99 will cause a little oddness in the bugzilla stats. I do not think it's worth the time to mitigate that completely and we can work around any strangeness concerning Aug. 31st to Sept. 1st. If you think that will cause issues please let me know what scenarios you are thinking of where perfect stats around the 4.4 to 5.0 rename are needed. I am not clear on what the oddness will be. We have made these changes in the past from 3.5 & 3.99 to 4.0 and 4.99. I would suggest you use a similar method. If you mean that a number of wiki searches will no longer work, I will fix those after the change is complete. This complete. I've repeated the same updates as the 3.99 -> 4.99 transition so any stats outcomes should be as we expect. Michael, Please change all bugs from 4.4 to 5.0 and all bugs from 4.99 to 5.99. New names for milestone 4.4 and 4.99 is 5.0 and 5.99. Does not seem to be complete. Also, I missed that 4.2 M4 should have been removed from the pull down menu. Thanks, Please change all bugs from 4.4 to 5.0 and all bugs from 4.99 to 5.99. New names for milestone 4.4 and 4.99 is 5.0 and 5.99. does not seem to be done. Sorry, I've taken another pass at these updates and I believe I've tracked down all the remaining 4.4 and 4.99 bugs. 4.2_M4 is inactive now as well. |