Hey,
Thanks for the pandaPIparser work. This is a courtesy note that we have
published a downstream chengdu v0.2.0 fork/release that includes the
pandaPIparser source in-tree and absorbs upstream PR #21, with Robert P.
Goldman credited in our downstream history and release notes.
Chengdu repo: https://github.com/billosys/chengdu
Release: https://github.com/billosys/chengdu/releases/tag/v0.2.0
For pandaPIparser, the upstream identity recorded by the release is:
The reason for the fork/release shape is that upstream appears dormant, while
our downstream wolong work needs stable binary releases built from in-tree
source with reproducible provenance. The v0.2.0 release publishes Linux x86_64
and macOS arm64 tarballs plus SHA256SUMS, release-manifest.txt, and
THIRD-PARTY-LICENSES.
No maintainer action is requested here. This is just an FYI/courtesy breadcrumb
so the downstream release, absorbed PR credit, and import identity are easy to
find from the upstream tracker.
Thanks again.
Hey,
Thanks for the pandaPIparser work. This is a courtesy note that we have
published a downstream chengdu v0.2.0 fork/release that includes the
pandaPIparser source in-tree and absorbs upstream PR #21, with Robert P.
Goldman credited in our downstream history and release notes.
Chengdu repo: https://github.com/billosys/chengdu
Release: https://github.com/billosys/chengdu/releases/tag/v0.2.0
For pandaPIparser, the upstream identity recorded by the release is:
The reason for the fork/release shape is that upstream appears dormant, while
our downstream wolong work needs stable binary releases built from in-tree
source with reproducible provenance. The v0.2.0 release publishes Linux x86_64
and macOS arm64 tarballs plus SHA256SUMS, release-manifest.txt, and
THIRD-PARTY-LICENSES.
No maintainer action is requested here. This is just an FYI/courtesy breadcrumb
so the downstream release, absorbed PR credit, and import identity are easy to
find from the upstream tracker.
Thanks again.