Skip to content
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

Charm 7.0.1 #3814

Closed
wants to merge 2 commits into from
Closed

Charm 7.0.1 #3814

wants to merge 2 commits into from

Conversation

ericjbohm
Copy link
Contributor

Change License to Apache 2.0 with LLVM exceptions.
Otherwise unchanged from 7.0.0

matthiasdiener and others added 2 commits May 15, 2024 14:07
* Change license to Apache-2.0 with LLVM exceptions

* docs : add NOTICE file for legal disclaimer

* docs: Add CHANGES for license change only release 7.0.1

* Update NOTICE

* Update NOTICE

---------

Co-authored-by: Eric J Bohm <[email protected]>
Co-authored-by: Abhinav Bhatele <[email protected]>
@ericjbohm ericjbohm added this to the 7.0.1 milestone May 15, 2024
@ericjbohm ericjbohm self-assigned this May 15, 2024
What's new in Charm++ 7.0.1
================================================================================

This is a change license only release, with the following change:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

maybe:

Suggested change
This is a change license only release, with the following change:
This is a license-only release, with the following change:

@ericjbohm
Copy link
Contributor Author

Not sure how to set this up as a PR, merging onto main looks like a lot of changes, but this looks like we're trying to make a change to 7.0.

@ericjbohm
Copy link
Contributor Author

Not sure how to set this up as a PR, merging onto main looks like a lot of changes, but this looks like we're trying to make a change to 7.0.

For that matter, not sure if needs to be a PR, since it already exists as a branch in the repo, so anyone can just check it out and use it as normal.

@matthiasdiener
Copy link
Contributor

matthiasdiener commented May 15, 2024

Not sure how to set this up as a PR, merging onto main looks like a lot of changes, but this looks like we're trying to make a change to 7.0.

Maybe make the version number changes in this PR on top of main, then create a new branch charm-7.0.1 off of charm-7.0.0 and just cherry pick the version number/license commits into charm-7.0.1.

@ericjbohm
Copy link
Contributor Author

ericjbohm commented May 15, 2024 via email

@ericjbohm
Copy link
Contributor Author

no PR required.

@ericjbohm ericjbohm closed this Jun 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants