+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.
>
>

Reply via email to