We need to give our users some short-lived guarantee about backwards
compatibility because it is necessary for upgrade.
Can we agree
“All Traffic Control 2.y components will work with a Traffic Ops 3.0”
with the following constraints:
- 2.y is the last release in the 2.x train
- 3.0 is exactly 3.0 and not 3.1, 3.2, 3.3, etc. In 3.1 all the deprecated
2.x APIs can get removed.
(Alternately would be “all traffic control 3.0 components will work with a
Traffic Ops 2.y” but we normally upgrade TO first in each release cycle)
Without this promise, how else would we upgrade from 2 to 3?
—Eric
> On Jun 7, 2018, at 12:05 PM, Dave Neuman <[email protected]> wrote:
>
> Since we are increasing the major version, I would assume that 2.x
> components will not work with 3.x components. The reality may be that they
> do work together, but I wouldn't count on it.
>
> In addition to what was mentioned above I think that we should including
> deprecating support for the Traffic Ops UI in 3.0. Once 3.0 is released we
> should only be using Traffic Portal as our UI.
>
> With that being said, +1 on the move to 3.0
>
> Thanks,
> Dave
>
> On Thu, Jun 7, 2018 at 8:48 AM, Eric Friedrich (efriedri) <
> [email protected]> wrote:
>
>> For those of us already on Centos7, what does this mean for compatibility
>> between TC releases?
>>
>> On Centos7, will we be able to use 3.0 with 2.x releases as is currently
>> done today.
>>
>> If already on Centos7, What is the upgrade story from 2.2 to 3.0?
>>
>> —Eric
>>
>>> On Jun 5, 2018, at 12:03 PM, 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
>>
>>
