I'm calling this vote as passed as we received no -1s and 6 +1s. Thanks to everyone for participating in the discussion, and as mentioned, our hope is that the transition is as painless as possible.
We will coordinate the actual act of updating to 3.0.0 so that it isn't a surprise when the commit comes through. I was planning to do this myself, perhaps next week. -- Thanks, Jeff On Fri, Jun 8, 2018 at 9:35 AM, Dan Kirkwood <[email protected]> wrote: > +1 > > On Fri, Jun 8, 2018 at 9:19 AM Eric Friedrich (efriedri) <[email protected]> > wrote: > >> +1 >> >> With the caveat that we maintain an upgrade process when we start >> deprecating APIs between components. >> >> —Eric >> >> > On Jun 7, 2018, at 2:11 PM, Dewayne Richardson <[email protected]> >> wrote: >> > >> > +1, this will allow us to do a better job with the API's >> > >> > On Tue, Jun 5, 2018 at 10:03 AM Jeff Elsloo <[email protected]> wrote: >> > >> >> In light of the major changes introduced into Traffic Router with PR >> >> 2331, I would like to call a vote to increase the major version of the >> >> project to 3.0.0. Also note that this version would represent the >> >> first release without official support for CentOS 6.x, though >> >> components might still continue to work. From 3.0.0 forward, only >> >> CentOS 7.x will be officially supported by the project. >> >> >> >> This impacts versioning of all components, so if other components are >> >> not ready to make major breaking changes during this transition, we >> >> would need to do so under another major version change in the future. >> >> >> >> I'd like to call this vote on Friday, so I will leave this open for 72 >> >> hours. >> >> -- >> >> Thanks, >> >> Jeff >> >> >> >>
