+1 (binding)

- Valid download links
- Valid checksums and PGP signatures.
- Source code does not contain "RC" terms.
- Correct LICENSE and NOTICE files.
- No unlicensed or pre-built binaries.


On Mon, Mar 9, 2026 at 4:30 PM Mohammad Sadoghi <[email protected]>
wrote:

> +1 binding
>
> - Download links are valid.
> - Signatures are valid.
> - Source distribution names ok.
> - LICENSE and NOTICE files are correct.
> - No pre-built binaries in the source archive.
> - Ecosystem components are ok.
>
>
> Best Regards,
> Mohammad Sadoghi, PhD
> Associate Professor, Chancellor's Fellow
> Exploratory Systems Lab (ExpoLab)
> Department of Computer Science
> University of California, Davis
>
>
> On Mon, Mar 9, 2026 at 16:27 Harish Gokul <[email protected]> wrote:
>
> > +1 (binding)
> >
> > Checklist completed:
> >
> > [✓] Download links are valid.
> > [✓] Checksums and PGP signatures are valid.
> > [✓] Source code does not contain "RC" terms.
> > [ ✓ ] LICENSE and NOTICE files are present and correct (including
> > incubating notice)
> > [✓] Ecosystem components' integration is good.
> > [✓] No unlicensed or pre-built binaries are included in the source
> archive.
> >
> > Best Regards,
> > Harish Krishnakumar
> >
> > On Mon, Mar 9, 2026 at 3:55 PM Bismanpal Singh Anand <
> [email protected]>
> > wrote:
> >
> > > Hi all,
> > > I’d like to propose a release candidate for Apache
> > ResilientDB(incubating)
> > > version 1.12.0-incubating-rc3.
> > >
> > > Release candidate details:
> > >
> > >   Version: 1.12.0-incubating
> > >   RC: rc3
> > >   Git tag: v1.12.0-incubating-rc3
> > >
> > > *Changes since rc2 : *
> > > This RC addresses issues raised during the previous vote. The KEYS
> > > publication issue has been fixed by adding the release signing key to
> the
> > > official KEYS file in the release distribution area. The source header
> > > issue identified during IPMC review has also been resolved.
> Additionally,
> > > unused previous RC directories were cleaned up from the staging area to
> > > avoid confusion during verification.
> > >
> > > *Release highlights:*
> > >
> > > - Added a PoC implementation for securing consensus against long-range
> > > attacks via collaboration.
> > > - Introduced LevelDB as a persistent storage backend to significantly
> > > improve recovery time.
> > > - Added license header support to existing configuration formats.
> > > - Removed committed public/private certificate files from the source
> > > distribution and replaced them with a setup-time key generation script.
> > >
> > > - Improved GraphQL server compatibility with the new configuration
> format
> > > and fixed a Python SDK GraphQL issue.
> > > - Automated deployment of ecosystem tools (ResLens, Beacon, Nexus,
> etc.)
> > > via GitHub Actions and Vercel.
> > > - Added an automated documentation generation workflow using
> Pocketflow.
> > > - ResInsight, an MCP server for exploring the ResilientDB ecosystem
> > > is added, It provides an educational assistant and knowledge-base
> > > integration, with documentation, quick start, and licensing in place.
> > > - Enhanced ecosystem tools including ResLens (profiling), Beacon
> > > (documentation), Nexus (RAG for consensus research), GraphQ-LLM, and
> the
> > > ResilientDB MCP server.
> > >
> > > The release candidate artifacts (SVN revision: 82941) are staged at:
> > >
> > >
> > >
> >
> https://dist.apache.org/repos/dist/dev/incubator/resilientdb/1.12.0-incubating-rc3/
> > > <
> > >
> >
> https://l.gotourl.es/l/c4d3826015c36d44f19fdfd4ee741ac94b1c4755?u=12264691
> > > >
> > >
> > > Release GitHub repository:
> > >
> > >
> > >
> >
> https://github.com/apache/incubator-resilientdb/releases/tag/v1.12.0-incubating-rc3
> > > <
> > >
> >
> https://l.gotourl.es/l/31f71221ce73fbe51849186f1dc4b99d72902317?u=12264691
> > > >
> > >
> > > KEYS file for verification:
> > >
> > > https://downloads.apache.org/incubator/resilientdb/KEYS
> > > <
> > >
> >
> https://l.gotourl.es/l/aadf2102248e50ae36a376f298d2f3484466a464?u=12264691
> > > >
> > >
> > > The vote will be open for at least 72 hours or until the necessary
> number
> > > of
> > > votes is reached.
> > >
> > > Please vote accordingly:
> > >
> > >   [ ] +1 approve
> > >   [ ] +0 no opinion
> > >   [ ] -1 disapprove (please provide reasoning)
> > >
> > > Checklist for reference:
> > >
> > >   [ ] Download links are valid.
> > >   [ ] Checksums and PGP signatures are valid.
> > >   [ ] Source distribution names match the proposed release version.
> > >   [ ] LICENSE and NOTICE files are present and correct (including
> > > incubating notice).
> > >   [ ] All source files have appropriate license headers where required.
> > >   [ ] No unlicensed or pre-built binaries are included in the source
> > > archive.
> > >   [ ] Ecosystem components are properly integrated without duplicating
> > > Apache project files.
> > >
> > > -
> > > Thanks,
> > > Bismanpal Singh Anand
> > >
> >
>


-- 
Best Regards,
Dakai Kang, PhD Candidate
Exploratory Systems Lab (ExpoLab)
Department of Computer Science
University of California, Davis

Reply via email to