You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@trafficcontrol.apache.org by "Gray, Jonathan" <Jo...@comcast.com.INVALID> on 2022/01/06 18:00:31 UTC
Re: [EXTERNAL] Re: 6.1.0 Planning
With 6.1.0 should API 4.0 be considered stable or is there still outstanding work in flight?
Jonathan G
From: Zach Hoffman <zr...@apache.org>
Date: Thursday, January 6, 2022 at 10:09 AM
To: dev@trafficcontrol.apache.org <de...@trafficcontrol.apache.org>
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 <zr...@apache.org> 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 <fr...@alum.rpi.edu> 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 <mi...@gmail.com> wrote:
> > >
> > > +1
> > >
> > > On Thu, Jan 6, 2022 at 9:13 AM Zach Hoffman <zr...@apache.org> wrote:
> > >
> > > > Planning to cut the 6.1.0 release branch from master on Tuesday, January
> > > > 11.
> > > >
> > > > -Zach
> > > >
Re: [EXTERNAL] Re: 6.1.0 Planning
Posted by Rawlin Peters <ra...@apache.org>.
We don't necessarily need an unstable API v5 in order to declare API
v4 stable. We could declare v4 stable, ditch v3 and below, and never
introduce a v5. One of the major reasons behind having an unstable API
version in the first place is to avoid
yet-another-major-TO-API-version to maintain. If we know of breaking
changes coming down the pipeline, we should hold off on stabilizing
until we can get those in. Once we don't have any absolutely necessary
breaking changes in the pipeline, we should stabilize. As far as I
know, that's just Layered Profiles right now (as Jeremy said). There
are definitely more things we COULD break to improve the API, but I'm
not sure those are a SHOULD at this point.
Basically, what we need to avoid is:
1) all new features requiring a new major TO API version -- we should
prefer non-breaking if possible
2) fragmenting breaking changes across multiple API versions -- we
should batch breaking changes into the same API version
- Rawlin
On Mon, Jan 10, 2022 at 1:06 PM Zach Hoffman <zr...@apache.org> wrote:
>
> Right, API v4 would only become stable if we have an unstable API v5,
> which we yet do not.
>
> -Zach
>
> On Mon, Jan 10, 2022 at 1:02 PM Jeremy Mitchell <mi...@gmail.com> wrote:
> >
> > @jonathan - the in progress "layered server profiles
> > <https://github.com/apache/trafficcontrol/blob/master/blueprints/layered-profile-server.md>"
> > requires 4.0 remain unstable if i recall correctly, therefore, TC 6.1 will
> > still have an unstable API 4.0. maybe our next release for march is 7.0
> > with a stable api 4.0 and an unstable 5.x?
> >
> > On Thu, Jan 6, 2022 at 11:01 AM Gray, Jonathan
> > <Jo...@comcast.com.invalid> wrote:
> >
> > > With 6.1.0 should API 4.0 be considered stable or is there still
> > > outstanding work in flight?
> > >
> > > Jonathan G
> > >
> > > From: Zach Hoffman <zr...@apache.org>
> > > Date: Thursday, January 6, 2022 at 10:09 AM
> > > To: dev@trafficcontrol.apache.org <de...@trafficcontrol.apache.org>
> > > 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 <zr...@apache.org> 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 <fr...@alum.rpi.edu>
> > > 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 <mi...@gmail.com>
> > > wrote:
> > > > > >
> > > > > > +1
> > > > > >
> > > > > > On Thu, Jan 6, 2022 at 9:13 AM Zach Hoffman <zr...@apache.org>
> > > wrote:
> > > > > >
> > > > > > > Planning to cut the 6.1.0 release branch from master on Tuesday,
> > > January
> > > > > > > 11.
> > > > > > >
> > > > > > > -Zach
> > > > > > >
> > >
Re: [EXTERNAL] Re: 6.1.0 Planning
Posted by Zach Hoffman <zr...@apache.org>.
Right, API v4 would only become stable if we have an unstable API v5,
which we yet do not.
-Zach
On Mon, Jan 10, 2022 at 1:02 PM Jeremy Mitchell <mi...@gmail.com> wrote:
>
> @jonathan - the in progress "layered server profiles
> <https://github.com/apache/trafficcontrol/blob/master/blueprints/layered-profile-server.md>"
> requires 4.0 remain unstable if i recall correctly, therefore, TC 6.1 will
> still have an unstable API 4.0. maybe our next release for march is 7.0
> with a stable api 4.0 and an unstable 5.x?
>
> On Thu, Jan 6, 2022 at 11:01 AM Gray, Jonathan
> <Jo...@comcast.com.invalid> wrote:
>
> > With 6.1.0 should API 4.0 be considered stable or is there still
> > outstanding work in flight?
> >
> > Jonathan G
> >
> > From: Zach Hoffman <zr...@apache.org>
> > Date: Thursday, January 6, 2022 at 10:09 AM
> > To: dev@trafficcontrol.apache.org <de...@trafficcontrol.apache.org>
> > 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 <zr...@apache.org> 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 <fr...@alum.rpi.edu>
> > 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 <mi...@gmail.com>
> > wrote:
> > > > >
> > > > > +1
> > > > >
> > > > > On Thu, Jan 6, 2022 at 9:13 AM Zach Hoffman <zr...@apache.org>
> > wrote:
> > > > >
> > > > > > Planning to cut the 6.1.0 release branch from master on Tuesday,
> > January
> > > > > > 11.
> > > > > >
> > > > > > -Zach
> > > > > >
> >
Re: [EXTERNAL] Re: 6.1.0 Planning
Posted by Jeremy Mitchell <mi...@gmail.com>.
@jonathan - the in progress "layered server profiles
<https://github.com/apache/trafficcontrol/blob/master/blueprints/layered-profile-server.md>"
requires 4.0 remain unstable if i recall correctly, therefore, TC 6.1 will
still have an unstable API 4.0. maybe our next release for march is 7.0
with a stable api 4.0 and an unstable 5.x?
On Thu, Jan 6, 2022 at 11:01 AM Gray, Jonathan
<Jo...@comcast.com.invalid> wrote:
> With 6.1.0 should API 4.0 be considered stable or is there still
> outstanding work in flight?
>
> Jonathan G
>
> From: Zach Hoffman <zr...@apache.org>
> Date: Thursday, January 6, 2022 at 10:09 AM
> To: dev@trafficcontrol.apache.org <de...@trafficcontrol.apache.org>
> 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 <zr...@apache.org> 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 <fr...@alum.rpi.edu>
> 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 <mi...@gmail.com>
> wrote:
> > > >
> > > > +1
> > > >
> > > > On Thu, Jan 6, 2022 at 9:13 AM Zach Hoffman <zr...@apache.org>
> wrote:
> > > >
> > > > > Planning to cut the 6.1.0 release branch from master on Tuesday,
> January
> > > > > 11.
> > > > >
> > > > > -Zach
> > > > >
>