Arnold - “Verified” is the proper term in my opinion. See what I wrote
Verified: YES (built locally, verified the keys, started the server, got the expected responses) I did not test the functionality, but the build passes tests. Binding (PMC member) On Mon, Oct 20, 2025 at 12:18 PM Arnold Galovics < [email protected]> wrote: > Guys, > > +1 from me too, but when people say "tested", do we know what kind of > testing is supposed to happen? I feel like we just have this feeling of the > package being tested, but in reality it cannot be considered actual > functional verification (if that's what's supposed to happen). > > In my mind, functional testing is part of the pipeline and every commit > making into the develop branch has to pass all the tests, it's a quality > gate. Therefore by logic, whatever commit we pick for releasing is passing > the quality gates hence no need for manual testing. What am I missing? > > Best, > Arnold > > Arnold Gálovics > > *CEO, Co-Founder* > > *+36 30 904 1885* > > https://docktape.com > > Docktape Technologies > > > > > On Sun, Oct 19, 2025 at 6:02 PM Terence Monteiro <[email protected]> > wrote: > >> For the record, >> GPG key verification successful as well >> >> -Terence Monteiro >> Member, PMC >> >> On Sun, Oct 19, 2025 at 9:04 PM Terence Monteiro < >> [email protected]> wrote: >> >>> +1 binding >>> Verified SHA512 checksums >>> Build successful on Ubuntu 22.04.4 LTS >>> Got warnings (attached STDERR log) >>> >>> Regards, >>> Terence Monteiro. >>> >>> >>> On Sat, Oct 18, 2025 at 8:17 PM Ahmed Adel <[email protected]> >>> wrote: >>> >>>> +1 >>>> Tested: YES >>>> >>>> Regards, >>>> Ahmed Adel >>>> >>>> On Sat, 18 Oct 2025 at 16:34, Felix van Hove <[email protected]> >>>> wrote: >>>> >>>>> +1, Verified: YES (built locally, verified keys, started server, >>>>> tested >>>>> responses via Swagger) >>>>> >>>>> On 17/10/2025 22:21, Ed Cable wrote: >>>>> > +1, not tested >>>>> > PMC member >>>>> > >>>>> > On Fri, Oct 17, 2025 at 1:10 PM VICTOR MANUEL ROMERO RODRIGUEZ < >>>>> > [email protected]> wrote: >>>>> > >>>>> >> +1 >>>>> >> >>>>> >> - Verified: YES >>>>> >> - I have tested the functionality. >>>>> >> - PMC member >>>>> >> >>>>> >> El vie, 17 oct 2025 a las 13:50, Aleksandar Vidakovic (< >>>>> >> [email protected]>) escribió: >>>>> >> >>>>> >>> +1, not tested >>>>> >>> >>>>> >>> On Fri, Oct 17, 2025 at 8:54 PM James Dailey <[email protected]> >>>>> wrote: >>>>> >>> >>>>> >>>> +1, Verified: YES (built locally, verified the keys, started the >>>>> server, >>>>> >>>> got the expected responses) >>>>> >>>> I did not test the functionality, but the build passes tests. >>>>> >>>> Binding (PMC member) >>>>> >>>> >>>>> >>>> *We need at least three binding votes. Voting has been open for >>>>> nearly >>>>> >>>> a week. * >>>>> >>>> >>>>> >>>> And, we would like others to do this, even if not on the PMC, we >>>>> need >>>>> >>>> you to verify the release. >>>>> >>>> If you are new to the list, give it a try. See start of thread for >>>>> >>>> instructions please. >>>>> >>>> >>>>> >>>> >>>>> >>>> >>>>> >>>> >>>>> >>>> >>>>> >>>> >>>>> >>>> On Wed, Oct 15, 2025 at 5:47 AM Bharath Gowda <[email protected]> >>>>> wrote: >>>>> >>>> >>>>> >>>>> +1, Tested: NO >>>>> >>>>> >>>>> >>>>> Regards, >>>>> >>>>> Bharath >>>>> >>>>> Lead Implementation Analyst | Mifos Initiative >>>>> >>>>> PMC Member | Apache Fineract >>>>> >>>>> Mobile: +91.7019635592 >>>>> >>>>> http://mifos.org <http://facebook.com/mifos> >>>>> >>>>> <http://www.twitter.com/mifos> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> On Tue, Oct 14, 2025 at 10:42 PM Adam Monsen < >>>>> [email protected]> >>>>> >>>>> wrote: >>>>> >>>>> >>>>> >>>>>> +1, Tested: YES >>>>> >>>>>> >>>>> >>>>>> >>>>> >>>>>> On 10/11/25 18:46, Adam Monsen wrote: >>>>> >>>>>> >>>>> >>>>>> Hello everyone, >>>>> >>>>>> >>>>> >>>>>> We are proud to present Apache Fineract 1.13.0, with the >>>>> artifacts >>>>> >>>>>> below up for a vote. Releases are important for a number of >>>>> reasons: They >>>>> >>>>>> put a stamp of approval on a set of code changes and they build >>>>> momentum >>>>> >>>>>> for future improvements. >>>>> >>>>>> >>>>> >>>>>> Release notes and ChangeLog >>>>> >>>>>> < >>>>> https://cwiki.apache.org/confluence/display/FINERACT/1.13.0+-+Apache+Fineract >>>>> > >>>>> >>>>>> >>>>> >>>>>> Source and binary artifacts >>>>> >>>>>> <https://dist.apache.org/repos/dist/dev/fineract/1.13.0/> >>>>> >>>>>> >>>>> >>>>>> Tagged as 1.13.0 >>>>> >>>>>> >>>>> >>>>>> Committer PGP keys, including the release signing key: >>>>> >>>>>> https://dist.apache.org/repos/dist/dev/fineract/KEYS >>>>> >>>>>> >>>>> >>>>>> Note that this release candidate contains source and binary >>>>> artifacts. >>>>> >>>>>> >>>>> >>>>>> This vote will be open for 72 hours: >>>>> >>>>>> >>>>> >>>>>> [ ] +1 approve >>>>> >>>>>> [ ] +0 no opinion >>>>> >>>>>> [ ] -1 disapprove (and reason why) >>>>> >>>>>> >>>>> >>>>>> Please indicate if you are a binding vote (member of the PMC). >>>>> Note: >>>>> >>>>>> PMC members are required to download, compile, and test the >>>>> artifacts >>>>> >>>>>> before submitting their +1 vote. >>>>> >>>>>> >>>>> >>>>>> Please also indicate with "Tested: YES/NO/PARTIAL" if you have >>>>> locally >>>>> >>>>>> built and/or tested these artifacts and/or a clone of the code >>>>> checked out >>>>> >>>>>> to the release commit, following the form: >>>>> >>>>>> >>>>> >>>>>> Tested: YES ... Verified integrity and signatures of release >>>>> artifacts >>>>> >>>>>> locally, built from source, ran jar/war: Did everything >>>>> mentioned in the current >>>>> >>>>>> release candidate verification guidance >>>>> >>>>>> <https://fineract.apache.org/docs/rc/#_artifact_verification>. >>>>> If you >>>>> >>>>>> did more than that, please specify. >>>>> >>>>>> >>>>> >>>>>> Tested: NO ... No testing performed on release candidate, e.g. >>>>> relying >>>>> >>>>>> on testing performed by other contributors and/or output of >>>>> GitHub Actions, >>>>> >>>>>> while exercising my right to vote. >>>>> >>>>>> >>>>> >>>>>> Tested: PARTIAL ... Please specify. >>>>> >>>>>> >>>>> >>>>>> >>>>> > >>>>> >>>>>
