12746 2018-05-11 13:43:44 +0000 Fix and Add/Remove Milestones 2018-05-16 11:20:14 +0000 1 1 5 Infrastructure Bugzilla bugzilla unspecified x86 Multiple RESOLVED FIXED Medium+ normal Q2 1 sjolley.yp.pm mhalstead infras.bug.watcher Infras.watcher --- --- No (bug/feature does not impact docs) oldest_to_newest 80572 0 sjolley.yp.pm 2018-05-11 13:43:44 +0000 Michael, Please add 2.5.1 and 2.7 as new milestones. Please review bug #12434. I can't set it to 2.6 M1. Not sure why. Please remove 2.1.4, 2.2.2, 2.2.3, 2.3.2, 2.3.3, 2.4, 2.4.1, 2.5, 2.5 M3, 2.5 M4 form the pull down selections. Thanks, Stephen 80591 1 mhalstead 2018-05-16 08:37:22 +0000 New versions and milestones are created for 2.5.1 and 2.7. 2.1.4, 2.2.2, 2.2.3, 2.3.2, 2.3.3, 2.4, 2.4.1, 2.5, 2.5 M3, 2.5 M4 are globally inactive. As for bug #12434, Pseudo is a separate project and was versioned differently so versions and milestones don't match the other products. Is this being managed in lockstep with YPcore now? I can add all currently active versions and milestones to Pseudo. 80596 2 sjolley.yp.pm 2018-05-16 09:20:04 +0000 Yes, please make the versions match for Pseudo. 80599 3 mhalstead 2018-05-16 11:20:14 +0000 I've added all active milestones to Pseudo which should allow for triage. After speaking with RP I've confirmed Pseudo has different versions from YP so those will not match. Your process doesn't depend heavily on the version number as far as I know so I hope this will work.