Sounds good, Nick. Unless there are objections, I'll add an EOL
September 30, 2022 for the 1.x branch on our github README and maybe
our site somewhere?
>I'm not keen on adding new features to 1.x, as that'll only encourage
people to stick on the old one, but I wouldn't go as far as -1'ing other
people's backports if they're still keen, at least for a while!
Agreed.
Onwards!
Cheers,
Tim
On Wed, Dec 15, 2021 at 10:01 AM Nick Burch <apa...@gagravarr.org> wrote:
>
> On Wed, 15 Dec 2021, Tim Allison wrote:
> > I think we should keep the 1.x branch open for security upgrades for a
> > bit...middle of next year? I have _not_ been adding new features or
> > even some bug fixes to 1.x, and I encourage people to migrate to 2.x.
>
> We've seen quite a few queries from people struggling to upgrade in the
> last few weeks, so I think it's fair to say we must have a decent number
> of 1.x users still. For an example, Alfresco only upgraded a couple of
> weeks ago, and that's only on their main branch, so it'll be a while until
> it's in their releases.
>
> I'm not keen on adding new features to 1.x, as that'll only encourage
> people to stick on the old one, but I wouldn't go as far as -1'ing other
> people's backports if they're still keen, at least for a while!
>
> I'd be minded to say we probably need to keep on top of security stuff
> until something like September 2022, to give people just over a year to
> upgrade to 2.x. I'm minded to say we allow anyone keen to backport
> bugfixes etc until 3 months before that, but effectively discourage it for
> the last part to help encourage hold-outs to move. I think we should post
> something on the site about the planned EOL timeline, linking once more to
> the wonderful migrating resource on the wiki.
>
> Nick
