Hi PJ,

Thanks, that's a fair point. I should have shared the release plan up front, 
and my last reply only gave a couple of examples instead of the full list.

0.2.2 is a source-only release, so I won't be publishing Desktop or npm 
packages for it. No convenience binaries have been published for any Apache 
Maka release so far, including 0.2.0.

Starting with the next release, I'll include the Desktop packages (macOS 
arm64/x64, Windows x64, Linux x64/arm64) and the npm package in the RC vote, 
built from the RC tag so they can be reviewed alongside the source.

For the retrospective review, here is the complete list of development builds 
published so far:

GitHub prereleases (https://github.com/apache/maka/releases), tagged 
v<version>-dev.<n>.<date>. Each release note records the commit it was built 
from:
- 0.2.0-dev: 9, 10, 11, 12, 15, 16, 19, 20, 22, 23, 25, 26, 27, 28, 30, 31, 35, 
36, 37, 38, 39, 41, 42, 43, 44, 46, 47, 48, 49, 51, 52, 53, 62, 64, 76, 77, 78
- 0.2.1-dev: 85, 88, 89, 91
- 0.2.2-dev: 92
- deps-v8-150.4.0-35e4d3471: prebuilt V8 static libraries used to build the 
Desktop app, with their notices

npm maka-agent (https://www.npmjs.com/package/maka-agent?activeTab=versions), 
versioned <version>-dev.<n>.<date> and described as developer snapshots:
- 0.2.0-dev: 3, 4, 5, 6, 8, 9, 10, 11, 12, 14, 15, 16, 18, 19, 20, 21, 22, 23, 
24, 25, 26, 27, 28, 29, 30, 31, 32, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 
45, 46, 47, 48, 49, 50, 51, 52, 53, 62, 64, 67, 68, 69, 70, 74, 75, 76, 77, 78, 
79
- 0.2.1-dev: 80, 82, 83, 84, 85, 86, 87, 88, 89, 90, 91
- 0.2.2-dev: 92, 97, 98, 99
- 0.0.0-alpha.0 and 0.1.0-beta.1: early placeholders, now deprecated
- 0.0.0-placeholder.1 and 0.0.0-placeholder.2: empty placeholders; latest 
points to placeholder.2

I'll also update the README as discussed.

Thanks,
Yuhan Lei
Apache ID: astrohan

On 2026-10-26 11:52 UTC PJ Fanning wrote:
> The convenience binaries get voted on. Not just source releases.
> You should need to review previous release votes on this mailing list
> and you'll see that other PPMCs are up front about their release
> plans.
> These are guidelines but we can't check them if we don't know what you
> are releasing.
> https://incubator.apache.org/guides/distribution.html
> 
> On Mon, 26 Oct 2026 at 11:40, Yuhan Lei <[email protected]> wrote:
> >
> > Hi PJ,
> >
> > Thanks for checking!
> >
> > I only linked the source candidate because this is a source release
> > vote. Here are the existing development builds for review:
> >
> > Desktop:
> > https://github.com/apache/maka/releases/tag/v0.2.0-dev.78.20261010
> > https://github.com/apache/maka/releases/tag/v0.2.1-dev.91.20261018
> >
> > npm:
> > https://www.npmjs.com/package/maka-agent?activeTab=versions
> >
> > These are development snapshots, not binaries of an approved source
> > release. There are no final 0.2.0 or 0.2.1 npm versions published. The
> > npm development builds use the `nightly` tag, and `latest` points to
> > an empty placeholder. I understand that the licensing requirements
> > still apply.
> >
> > Agreed on the README. I'll put the approved source archive first for
> > users building from source, and keep the Git checkout instructions in
> > the development section.
> >
> > For nightlies, I previously compared download speeds and found GitHub
> > substantially faster than nightlies.apache.org. I chose GitHub to make
> > testing easier and reuse its free infrastructure rather than add load
> > to ASF servers. The builds are marked as prereleases and include the
> > incubation disclaimer and a note that they are not approved Apache
> > releases.
> >
> > Thanks,
> > Yuhan Lei
> > Apache ID: astrohan
> >
> > <[email protected]> 于2026年10月24日周六 18:19写道:
> > >
> > > Hi everyone,
> > >
> > > I'd like to request IPMC approval for Apache Maka 0.2.2 (incubating), 
> > > release candidate 2.
> > >
> > > The PPMC vote is running concurrently on [email protected]:
> > > https://lists.apache.org/thread/s248h74ok3t023gox886bxbodhh7ds12
> > >
> > > RC2 replaces the withdrawn RC1 and includes security dependency updates 
> > > and release fixes.
> > >
> > > Source candidate:
> > > https://dist.apache.org/repos/dist/dev/incubator/maka/0.2.2-incubating-rc2/
> > >
> > > Tag:
> > > https://github.com/apache/maka/tree/v0.2.2-incubating-rc2
> > >
> > > Source commit:
> > > eeeae5128cdc7e498e2c8cae0881f138df3d8301
> > >
> > > KEYS:
> > > https://downloads.apache.org/incubator/maka/KEYS
> > >
> > > Signing key fingerprint:
> > > CCF8C3FDF7351B68084BFA1D975D5AA38DC0BCFA
> > >
> > > The source-candidate workflow passed installation, dependency auditing, 
> > > build, type checks and tests from a clean extraction:
> > > https://github.com/apache/maka/actions/runs/40071829596
> > >
> > > I also reproduced the source payload locally from the tag and verified 
> > > the checksum and signature after downloading the staged files again.
> > >
> > > The production and shipped-dependency audits found no moderate-or-higher 
> > > advisories. Two low-severity npm audit entries remain for KaTeX and its 
> > > use through Mermaid. DISCLAIMER-WIP is included in the source archive.
> > >
> > > This vote covers the source release only. Please download, verify, build 
> > > and test the candidate, then vote:
> > >
> > > [ ] +1 Approve this release
> > > [ ] 0 No opinion
> > > [ ] -1 Do not approve (please provide the reason)
> > >
> > > The IPMC vote will remain open for at least 72 hours. Only IPMC votes are 
> > > binding for this approval. I will publish the release only after both 
> > > votes have passed.
> > >
> > > Thanks,
> > > Yuhan
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [email protected]
> > For additional commands, e-mail: [email protected]
> >
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
> 
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to