Gary, I think you misunderstood. It may be another week before I start the release. Yes, the build issues need to be addressed. I was laying out my process before starting a release. I am suggesting that there should be time to fix the build and look at PRs and Jira issues before the release is cut.
Ralph > On Sep 12, 2020, at 10:59 AM, Gary Gregory <garydgreg...@gmail.com> wrote: > > I think focusing on fixing the build should come before considering > bringing in PRs or Jira issues. I think Matt stated we don't get a clean > build ATM? > > Gary > > On Sat, Sep 12, 2020, 13:55 Ralph Goers <ralph.go...@dslextreme.com> wrote: > >> Yeah, I rely mostly on the automation but I run the build on my Mac >> several times before a release and if any of them fail I wouldn’t even >> start the release process. I still am working on my $dayjob project and >> would still want to take a look at open Jira issues before starting the >> release. I would suggest others use the time to look at open PRs and Jira >> issues for any that look a) important, b) easy to fix, or c) interesting >> to you and work on them. >> >> I guess it should be stated again that I use those 3 criteria when I am >> evaluating Jira issues. If they don’t fall into one of those categories for >> any of the committers they are never going to be fixed without a PR or >> someone paying someone to be interested. >> >> Ralph >> >>> On Sep 12, 2020, at 10:44 AM, Matt Sicker <boa...@gmail.com> wrote: >>> >>> 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> >>> >> >> >>
