Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Enterprise license, builds, release #3277

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
Tracked by #480
spikecurtis opened this issue Jul 28, 2022 · 1 comment · Fixed by #3517
Closed
Tracked by #480

Enterprise license, builds, release #3277

spikecurtis opened this issue Jul 28, 2022 · 1 comment · Fixed by #3517
Assignees

Comments

@spikecurtis
Copy link
Contributor

Problem

We need to be able to check in enterprise licensed code that doesn't get built from the AGPL entrypoints. We also need to include the enterprise license itself so that people can understand what rights they do and do not have if they use this code.

Implementation notes

We will add an enterprise/ directory that contains new main() entrypoints for all released binaries. For the purpose of this ticket, these binaries are functionally identical to the AGPL binaries, and the main() functions in enterprise should call into AGPL packages.

Acceptance Criteria

  1. New make targets that build enterprise variants of all the binaries we currently release. (We don't need enterprise variants of utilities in this issue.) Includes cross platform builds.
  2. Release scripts are switched to use enterprise builds. AGPL "release" is not required, only the ability to build binary targets for all supported platforms.
@kylecarbs
Copy link
Member

All of our build scripts should be enterprise by default, and therefore don't need to change the naming from my perspective.

I think for community-specific binary building we can have named steps, but I wouldn't want the inverse.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants