With 6.1.0 should API 4.0 be considered stable or is there still outstanding work in flight?
Jonathan G From: Zach Hoffman <[email protected]> Date: Thursday, January 6, 2022 at 10:09 AM To: [email protected] <[email protected]> Subject: [EXTERNAL] Re: 6.1.0 Planning If there's anything anyone else wants included in 6.1.0, let's try to get it in before the expected 6.1.0 release branch cut date 2021-01-11. -Zach On Thu, Jan 6, 2022 at 10:06 AM Zach Hoffman <[email protected]> wrote: > > In the 2021-01-04 TC working group, we went through open issues and > PRs and put together the 6.1.0 milestone > <https://urldefense.com/v3/__https://github.com/apache/trafficcontrol/milestone/19__;!!CQl3mcHX2A!XEggSAgJjuxCs_cjtUY4Lqa1Y4wdsC-fw0IpB_qsl1glGMFx4QvrrCSgGY9GPoDpAgs6$ > >: > - Replace github.com/dgrijalva/jwt-go with github.com/lestrrat-go/jwx/jwt > - Create a secure parameter read permission to be able to see the > values of secure parameters > - Remove postgresql13-devel package dependency from Traffic Ops rpm > - Revert automatic log rotation Log4J configuration > > -Zach > > On Thu, Jan 6, 2022 at 10:04 AM Eric Friedrich <[email protected]> wrote: > > > > Sounds good, Thanks Zach. > > > > How's the state of master? Are we feeling good that its ready to cut a > > release off of? > > > > On Thu, Jan 6, 2022 at 11:16 AM Jeremy Mitchell <[email protected]> > > wrote: > > > > > > +1 > > > > > > On Thu, Jan 6, 2022 at 9:13 AM Zach Hoffman <[email protected]> wrote: > > > > > > > Planning to cut the 6.1.0 release branch from master on Tuesday, January > > > > 11. > > > > > > > > -Zach > > > >
