I’ll add another voice to those asking for the 6.2 LTS to be extended. We are currently using 6.2 in production and would need at least 3 months, preferably 6 to make the transition.
Also, can you please update the traffic server downloads page?[1] It still indicates 6.2 is the current LTS and 7.1 is just a stable latest release. (The News section on the front page is correct) Thanks, Eric [1]https://trafficserver.apache.org/downloads On May 30, 2018, at 1:26 AM, Zelkowitz, Evan <evan_zelkow...@comcast.com<mailto:evan_zelkow...@comcast.com>> wrote: The ugprade really isnt that bad (at least from what I heard of the experience from those who did the 6x upgrade before I did 7) If it helps you can skim my presentation from the traffic control summit: https://cwiki.apache.org/confluence/display/TC/2018+Spring+Summit+--+Boxborough%2C+MA Just go to the ATS@comcast presentation. With testing it can be done in a few months, its mostly knocking out the old variables, setting up the new logging, and the big one is the cacheurl to cachekey conversion since that needs testing depending on what types and how complex your cacheurl regexes are ________________________________________ From: Leif Hedstrom <zw...@apache.org> Sent: Tuesday, May 29, 2018 10:51 PM To: dev@trafficserver.apache.org Subject: [EXTERNAL] Re: [DISCUSS] Time to EOL 6.2.x? On May 29, 2018, at 10:47 PM, zzz <z...@apache.org> wrote: Team, We're still on 6.2.x and have the plan to migrate to a newer version later this year. However, the migration, from our previous experience, can take 6+ months. +1 on postponing the EOL for another 6 months, if it works for everybody. Still, someone would have to take on the RM responsibilities for this. — Leif Thanks, Zizhong 2018-05-29 20:52 GMT-07:00 Chao Xu <ok...@apache.org>: Hi Leif, I still working on 6.0.x branch and pushed a PR#3539 for 6.2.x recently. The PR#3539 fix a bug for hostdb from 2.0.x ~ 6.2.x. :-D - Oknet 2018-05-30 7:40 GMT+08:00 Leif Hedstrom <zw...@apache.org>: On May 29, 2018, at 17:10, salil GK <gksa...@gmail.com> wrote: We too are in 6.2.2 and plans are in place to upgrade to 7.x in short while. But it may take some 3-4 months. I would love to see 6.2.2 support extend for another 6 months - ( is it too much expectation ! ) I won’t oppose that, if there is a RM that is willing to do the work. Right now, I know of no active committers that are still on 6.x, and that’s a real problem. — Leif On 30 May 2018 at 03:43, Chris Lemmons <alfic...@gmail.com> wrote: So, I'd love to be +1 on kicking 6.2 to the curb. But we've got a team using 6.2 that doesn't have immediate plans to upgrade to 7. There's some relatively important stuff chilling out in the pending release of 6.2 that will be fairly important. Am I the only one? On Tue, May 29, 2018 at 1:50 PM, Leif Hedstrom <zw...@apache.org> wrote: Hi all, we have a few more weeks left on the expected LTS support cycle for 6.2.x. Are there any objections to officially EOL this release, say 2 weeks from now? So, we’d stop support for 6.2.x on June 15th 2018. If so, do we want to make one final 6.2.x release before such EOL? Is there anyone who needs it? :-) Thoughts? — Leif -- - Oknet Xu
