for a proper open source license compliance management it would be very helpful to have unique release bundles at the repository.
For me it is not clear, if the master branch is 2.08 stable or ongoing development and where the 2.07 ends in code.
It would be very very helpful to have releases at least for 2.07 and 2.08, because it seems there happens also the license change from proprietary Basic/Commercial license to MIT license (would be also helpful in the future e.g. for the buildroot project to get a proper versioned source code bundle).
BTW: The README.md points in "Obtaining cgic" to version 2.07 which returns HTTP 404.
Hi Tom,
for a proper open source license compliance management it would be very helpful to have unique release bundles at the repository. For me it is not clear, if the master branch is 2.08 stable or ongoing development and where the 2.07 ends in code.
It would be very very helpful to have releases at least for 2.07 and 2.08, because it seems there happens also the license change from proprietary Basic/Commercial license to MIT license (would be also helpful in the future e.g. for the buildroot project to get a proper versioned source code bundle).
BTW: The README.md points in "Obtaining cgic" to version 2.07 which returns HTTP 404.
Thank you very much.
Regards, Thorsten