+1 - It is important that the community that is asking for a release test it, especially in production. Phil, Leif, and I, the only people that voted for the release, do not have production servers running 6.2.x anymore.
-Bryan > On Aug 4, 2018, at 4:51 PM, Phil Sorber <sor...@apache.org> wrote: > > I didn't see this thread during the time it was active, it was just pointed > out to me, but I'll add my opinion now. We just made a 6.2.3 release that > had a bunch of important fixes in it, but 6.2.x is really old. No one is > doing new development on it. It has been a year since the previous release. > I think if people are looking to get off of it in 3-6 months, they should > do it regardless of the fact that no one is maintaining this release > anymore. If anything that should be motivation. My advice is maintain your > own local branch with any patches that you want on it. Feel free to use > GitHub PRs as a staging area for sharing patches. There are only 2 sitting > there right now and this is not a long term solution so I don't think it's > a terrible idea. We carried 6.2.x past our originally announced EOL date > and I think it's done now. I'd also like to echo Leif's point that he made > on the vote thread. We have no people testing 6.2.x. No one that was > running it or participated in this thread, voted. I can't see it being > really that important to have any more releases in the next 3-6 months. > > Thanks. > > On Tue, Jun 12, 2018 at 6:19 AM Susan Hinrichs <shinr...@oath.com.invalid> > wrote: > >> I see that oknet has a PR. I see PRs in total with the 6.2.3 milestone. >> >> While I am not working with 6.x anymore, I'm willing to work with Chris and >> others to shepherd in PRs to make new 6.x releases until the end of 2018. >> This would only be security fixes and very critical bug fixes. >> >> >> On Mon, Jun 11, 2018 at 4:54 PM, Chris Lemmons <alfic...@gmail.com> wrote: >> >>> I'm seeing a number of folks who'd like a stay of execution for ~6 >>> months on 6.2.x. Do we have a solid list of PRs we'd like to have >>> backported? >>> >>> On Wed, May 30, 2018 at 6:25 AM, Eric Friedrich (efriedri) >>> <efrie...@cisco.com> wrote: >>>> 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 >>>> >>>> >>>> >>> >>
signature.asc
Description: Message signed with OpenPGP
