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

frozen 1.6 with Apache commons 2.0 dual licence #60

Open
arnehaber opened this issue Sep 16, 2020 · 4 comments
Open

frozen 1.6 with Apache commons 2.0 dual licence #60

arnehaber opened this issue Sep 16, 2020 · 4 comments

Comments

@arnehaber
Copy link

You recently switched to Apache commons 2.0 license for frozen.

Can you create a 1.6-APL release under Apache commons 2.0 license as a fork from Tag 1.6? Or is there any GPL code in 1.6 so you are forced to have a GPL license?

@cpq
Copy link
Member

cpq commented Sep 16, 2020

Is the intention to have a release with the APL?
What if we just cut off the HEAD?

@arnehaber
Copy link
Author

We have currently the 1.6 in use. We assumed, that it has a Apache Commons 2.0 license, since we just checked the HEAD for the licence.
We tested our system with the 1.6. So if we change to the HEAD version of frozen, we have to repeat our tests.
Our preferred solution is to have a 1.6 under Apache Commons 2.0.

@cpq
Copy link
Member

cpq commented Sep 17, 2020

Repeating tests usually means running make test, which is not much to do :)
However there could be exceptions like paid certifications made against certain versions.

@arnehaber
Copy link
Author

On the SW level, yes. But on HW and system integration level, regression testing is more than make test.

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

No branches or pull requests

2 participants