Open band-a-prend opened 3 years ago
We could certainly make a first release version now. The FTL has been pretty stable for a number of years now and we use it extensively at SCM, so it also receives some real world testing. I have not made a release so far because internally we just use the master branch and I have not really found a compelling reason to make a release.
Would it help you in any way if the current master branch became FTL version 1.0?
It could show, in my view, to external users that project at some stable point; got new noticeable features or enhancements; and it simplifies a packaging for linux distributives, especially the naming of package versions.
E.g. for gentoo linux package it's no problem for packaging to fetch current master branch via git or get certain commit tarball but it's more suitable to have deal with fixed release and keep an eye on it.
Would it help you in any way if the current master branch became FTL version 1.0?
That would be great!
I packaged ftl
state on 2021-03-08
in Gentoo GURU (user repository) like dev-libs/ftl-1.0_p2021308. I could create package for live upsream but as QA requires passing user's system compiler flags it could become build broken sometimes on makefile significant changes.
Are the fixed release of Fortran Template Library planning?
Could it be fixed as release for for some early "feature" point by creation of git tag?