+1 to announce EOL of 2.5.x

On Wed, Mar 13, 2019 at 12:18 AM Huxing Zhang <hux...@apache.org> wrote:

> Hi,
>
> Given the EOL for 2.5.x has been discussed 10 months ago[1].
> I am +1 on shorten the period.
> One question, is 2.6.x completely compatible to 2.5.x?
>
>
> https://lists.apache.org/thread.html/d9384d891977994d39603d06cff6ba9ba3c9adc972d4733e4a9f987c@%3Cdev.dubbo.apache.org%3E
>
> On Fri, Mar 8, 2019 at 10:58 AM yuhang xiu <carry...@gmail.com> wrote:
> >
> > +1
> >
> > Ian Luo <ian....@gmail.com> 于2019年3月8日周五 上午10:42写道:
> >
> > > +1 to announce EOL of 2.5.x as soon as possible.
> > >
> > > On Thu, Mar 7, 2019 at 6:04 PM jun liu <ken.lj...@gmail.com> wrote:
> > >
> > > > > IMO, we should consider announce the end of life in the near
> future,
> > > > > say 1 year, and only support critical bug fix or security fix,
> > > >
> > > > In fact, 2.5.x has been out of the community’s daily maintenance for
> a
> > > > while. And I think few users are still staying on this branch, this
> can
> > > be
> > > > told from the PRs and issues reported as really few issues were
> related
> > > to
> > > > 2.5.x in the past 5-6 months.
> > > >
> > > > I think we should announce EOL plan ASAP and 3 months official buffer
> > > > period would be enough.
> > > >
> > > > Jun
> > > >
> > > > > On Mar 7, 2019, at 4:49 PM, Huxing Zhang <hux...@apache.org>
> wrote:
> > > > >
> > > > > Hi,
> > > > >
> > > > > I see someone send a pull request to 2.5.x branch[1].
> > > > > My question is that is 2.5.x branch still being supported?
> > > > > IMO, we should consider announce the end of life in the near
> future,
> > > > > say 1 year, and only support critical bug fix or security fix,
> while
> > > > > that we should provide a migration guide for user to upgrade from
> > > > > 2.5.x to 2.6.x or 2.7.x.
> > > > >
> > > > > What do you think?
> > > > >
> > > > > [1] https://github.com/apache/incubator-dubbo/pull/3565
> > > > >
> > > > > --
> > > > > Best Regards!
> > > > > Huxing
> > > >
> > > >
> > >
>
>
>
> --
> Best Regards!
> Huxing
>

Reply via email to