+1

I checked:
- 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,
Shaokang

On Wed, Feb 11, 2026 at 5:59 AM 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 Tue, Feb 10, 2026 at 13:49 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-rc2.
> >
> > Release candidate details:
> >
> >   Version: 1.12.0-incubating
> >   RC: rc2
> >   Git tag: v1.12.0-incubating-rc2
> >
> > *Changes since rc1 : *
> > This RC includes licensing and documentation updates plus a new ecosystem
> > tool. The LICENSE was updated to fix the third-party path for
> sanitize.css
> > (whole folder reference is done now); the DISCLAIMER was simplified per
> ASF
> > feedback. ResInsight, an MCP server for exploring the ResilientDB
> > ecosystem, was merged into the repo.
> >
> > *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: 82416) are staged at:
> >
> >
> >
> https://dist.apache.org/repos/dist/dev/incubator/resilientdb/1.12.0-incubating-rc2/
> > <
> >
> https://l.gotourl.es/l/b4830ae859b4dad7a2788708fe7ef40937fd30e7?u=12264691
> > >
> >
> > Release GitHub repository:
> >
> >
> https://github.com/apache/incubator-resilientdb/tree/v1.12.0-incubating-rc2
> > <
> >
> https://l.gotourl.es/l/77f25f95356ed3568ab86176adaf57aaf96ddb4d?u=12264691
> > >
> >
> > KEYS file for verification:
> >
> > https://dist.apache.org/repos/dist/dev/incubator/resilientdb/KEYS
> > <
> >
> https://l.gotourl.es/l/ec27b0ba978430a47e52899fd356fe5edf81705b?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
> >
>

Reply via email to