The thing about GitHub is it generates zip and tar.gz source archives
and allows access to them for every git tag and by extension every
GitHub release (which appears to be primarily just a way to attach
release notes to a git tag).
There are mechanisms to add additional artifacts too but with Burr and
Hamilton, all we seem to have are the source code artifacts.
I believe that there may be some ASF projects and podlings who use the
mechanisms to expose additional convenience artifacts on GitHub and we
probably should have policies for these.

Burr doesn't yet have an ASF release so the most recent release was
added to the GitHub project before the project was migrated to the
apache group in GitHub.
This explains the absence of a DISCLAIMER and NOTICE and the non Apache LICENSE.

Thee most recent Hamilton release on GitHub is an RC0 and that appears
to have the LICENSE, NOTICE and DISCLAIMER that I would expect.

On Sat, 2 May 2026 at 11:10, Justin Mclean <[email protected]> wrote:
>
> Hi,
>
> I also checked current podlings against the Incubator GitHub distribution 
> guidance:
> https://incubator.apache.org/guides/distribution.html#github
>
> The following podlings appear to have GitHub Releases that may need 
> cleanup/extra info added:
>  - Burr
>  - Casbin
>  - Fluss
>  - GraphAr
>  - Hamilton
>  - Iggy
>  - OzHera
>  - ResilientDB
>
> Again, this was done with a script and could be incomplete or incorrect.
>
> Could mentors and PPMCs please check that GitHub Releases include the 
> incubating disclaimer where needed, and that RCs, nightlies, and snapshots 
> etc are marked as GitHub pre-releases?
>
> Thanks,
> Justin
> ---------------------------------------------------------------------
> 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