I agree. I'd be glad to go through those as well, contact authors, and move everything without a milestone to either 2.2 or a future milestone (2.3? 2.x?). I can do that in the next few days, and then we can re-evaluate the timeline. Does that sound good?
On Wed, Jan 24, 2018 at 1:56 PM, Eric Friedrich (efriedri) < [email protected]> wrote: > Hey Rob- > Thanks for taking on the RM duties! > > We’ve got 22 major open bugs in Github Issues currently: > https://github.com/apache/incubator-trafficcontrol/issues?q=is% > 3Aopen+is%3Aissue+label%3Abug+label%3Amajor > <https://github.com/apache/incubator-trafficcontrol/issues?q=is:open+is:issue+label:bug+label:major> > > I see that a bunch of these bugs don’t have milestones assigned to them > today. I think we should triage these into must-fix for 2.2 vs 2.3 and then > make a judgment on when it makes the most sense to cut the release branch. > Otherwise we might be stuck doing a bunch of back porting of fixes in the > next month or so. > > —Eric > > > On Jan 24, 2018, at 3:47 PM, Robert Butts <[email protected]> wrote: > > Hi, > > I'm your friendly neighbourhood Release Manager for Traffic Control 2.2. > > We are getting ready to start the 2.2 branch of TC. We would like to do > this in the next 2 weeks. > > See https://github.com/apache/incubator-trafficcontrol/milestone/2 > > Are there any know issues that would prevent this from happening? > > Are there any features that can be wrapped up and go into this version? > > Any other comments or suggestions? > > Thanks, > > Robert Butts > > >
