skrawcz commented on issue #1336: URL: https://github.com/apache/hamilton/issues/1336#issuecomment-2913245035
> LICENSE, NOTICE and DISCLAIMER files that describe the contents of the binary artifacts (tailored to each binary artifact) Understood. We can first work on the main one - `sf-hamilton`. > Any 3rd party code or binaries included in the binary artifact needs to have a license compatible with the Apache one > The licenses for these 3rd party code or binaries need to be included Yeah the only package that bundles other things is `sf-hamilton-ui` that has one javascript package without a compatible license -- which we listed in the proposal. > hopefully binary artifact names are renamed to include apache and possibly, incubating in their names @pjfanning the main hamilton package is [published here](https://pypi.org/project/sf-hamilton/) on pypi under `sf-hamilton`. We need to maintain publishing under that for everyone. We could dual publish under sf-hamilton and apache-hamilton for a bit, and then make sf-hamilton a shell that just depends on apache-hamilton as a migration route for folks. Unfortunately, including `incubating` won't be possible. Thoughts? > all binary artifacts that Hamilton ships should be based on a source release - we can also do snapshot releases as long as they are badged as snapshot releases Yeah we can use git tags that match to the source used to create a release. We already do that manually. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
