Seems like one of the things we need to do before the release candidate is get all the tests passing again. I'll look more into any test failures introduced from my JUnit 5 refactoring. We do have test failures related to OSGi at the moment due to a dependency update, though that might be due to incompatible test infra more so than any production problem.
On Fri, 11 Sep 2020 at 09:49, Apache <ralph.go...@dslextreme.com> wrote: > > It is no problem. I have been heads down trying to get something done for > work. Should be soon though. > > Ralph > > > On Sep 11, 2020, at 4:40 AM, Volkan Yazıcı <volkan.yaz...@gmail.com> wrote: > > > > Hey Ralph! This is your friendly reminder for the pending 2.x release. > > (Apologies for the inconvenience.) > > > >> On Thu, Aug 27, 2020 at 3:55 PM Apache <ralph.go...@dslextreme.com> wrote: > >> > >> No, you are not expected to do anything else. While anyone can be the > >> release manager, typically I have been doing them. They take a fair amount > >> of time so I typically start them on a weekend when I have enough time. > >> > >> Ralph > >> > >>> On Aug 27, 2020, at 6:14 AM, Volkan Yazıcı <volkan.yaz...@gmail.com> > >> wrote: > >>> > >>> Would anybody mind giving some indication on an ETA, please? > >>> Or am I expected to do anything else further? > >>> > >>>> On Tue, Aug 25, 2020 at 1:59 PM Volkan Yazıcı <volkan.yaz...@gmail.com> > >>>> wrote: > >>>> > >>>> Yes, you read the subject right! I will appreciate it if people can > >> spare > >>>> some time on skimming through the change set one last time regarding > >> JTL. > >>>> > >>>> So... When are we gonna cut the ribbon for the upcoming 2.x release? > >>>> > >> > >> > >> > > -- Matt Sicker <boa...@gmail.com>
