frozen 1.6 with Apache commons 2.0 dual licence
arnehaber opened this issue · 4 comments
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?
Is the intention to have a release with the APL?
What if we just cut off the HEAD?
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.
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.
On the SW level, yes. But on HW and system integration level, regression testing is more than make test.