# Should fpm release versions more often **URL:** \ **Category:** Meta\ **Created:** [October 23, 2022, 12:55pm UTC](https://fortran-lang.discourse.group/t/should-fpm-release-versions-more-often/4596 "2022-10-23T12:55:03Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![gnikit](https://yyz2.discourse-cdn.com/free1/user_avatar/fortran-lang.discourse.group/gnikit/32/1213_2.png) [@gnikit](https://fortran-lang.discourse.group/u/gnikit)\ **Post date:** [October 23, 2022, 12:55pm UTC](https://fortran-lang.discourse.group/t/should-fpm-release-versions-more-often/4596/1 "2022-10-23T12:55:03Z")
I am curious if we should adopt a more frequent release schedule for fpm (and potentially other Fortran-lang projects). A while back I read a blog post [Major Version Numbers are Not Sacred](https://tom.preston-werner.com/2022/05/23/major-version-numbers-are-not-sacred.html) by Tom Preston-Werner creator of Semantic Versioning and it changed my perspective on releases. I think fpm releasing its updates more frequently to all its release channels, conda-forge, brew, etc. would greatly benefit its user base and growth as a build tool. ---
**Author:** ![awvwgk](https://yyz2.discourse-cdn.com/free1/user_avatar/fortran-lang.discourse.group/awvwgk/32/154_2.png) [@awvwgk](https://fortran-lang.discourse.group/u/awvwgk)\ **Post date:** [October 23, 2022, 2:58pm UTC](https://fortran-lang.discourse.group/t/should-fpm-release-versions-more-often/4596/2 "2022-10-23T14:58:48Z")
See [Establishing a release schedule · Issue #416 · fortran-lang/fpm · GitHub](https://github.com/fortran-lang/fpm/issues/416) for a previous suggestion. From the fpm side this was addressed by adding a continuous delivery workflow. I stand to what I wrote back then, which means whoever is contributing to fpm should be in charge of setting the pace of the releases. This also means any contributor is welcome to initiate a new release (best coordinated with other contributors), the workflow is described in detail at [Release Process · fortran-lang/fpm Wiki · GitHub](https://github.com/fortran-lang/fpm/wiki/Release-Process). ---
**Author:** ![everythingfunctional](https://yyz2.discourse-cdn.com/free1/user_avatar/fortran-lang.discourse.group/everythingfunctional/32/176_2.png) [@everythingfunctional](https://fortran-lang.discourse.group/u/everythingfunctional)\ **Post date:** [October 24, 2022, 12:29am UTC](https://fortran-lang.discourse.group/t/should-fpm-release-versions-more-often/4596/3 "2022-10-24T00:29:54Z")
I think there’s been a pretty impressive track record of not introducing bugs or breaking changes so far, so more frequent releases shouldn’t be a problem. However, I think the work on fpm has been somewhat sporadic, so we shouldn’t release so much on a schedule as much as just when something new is ready. That’s kind of a nebulous metric, so I think @awvwgk 's point is correct; let’s just create a release as soon as a feature is done that somebody would like to have available in a release, and any contributor is at liberty to call for that. ---
**Author:** ![gnikit](https://yyz2.discourse-cdn.com/free1/user_avatar/fortran-lang.discourse.group/gnikit/32/1213_2.png) [@gnikit](https://fortran-lang.discourse.group/u/gnikit)\ **Post date:** [October 25, 2022, 7:20pm UTC](https://fortran-lang.discourse.group/t/should-fpm-release-versions-more-often/4596/4 "2022-10-25T19:20:31Z")
The rolling release is great but I don’t think it addresses the distribution of fpm through its packaging tools e.g. conda-forge. What I was referring to was exactly this > [@awvwgk](#): > > This also means any contributor is welcome to initiate a new release (best coordinated with other contributors) Whether or not we should try and issue releases more often, not necessarily for every merged PR but whenever a new feature is added or certain bugs are fixed so people using brew and anaconda could have access to these features, which in turn will make detecting bugs easier since more users will be running an fpm version that is closer to the main branch. I am in the camp that releases should be often and incremental without massive Changelogs. PS For clarity purposes, I am not advocating for a periodic release schedule, just more frequent in terms of features added.