Create a release
Its been a while since we released a 'stable' version of sac2c. I don't see any reason to delay this, I think the compiler is pretty stable at the moment (seq, mt-pth, cuda targets seems to work fine).
Before we do this though, I think there are a few things we should consider:
- what do we name it? There hasn't been a devcamp in a while, so I guess we're going to have to get creative here...
- decide on some schedule, or conditions to help us get into the habit of making releases more regularly (last stable release is 1.3.3-MijasCosta)
- in #2269 (comment 10870), @rbe makes a really good point regarding actually documenting the changes in the compiler (especially new features!). This would help making it more clear how much work is going into the compiler, and what research activities this is driving. For example, we have two presentations at IFL2021 talking about new features that are in the pipeline to be merged in a some point. I think adding a CHANGELOG file to the repo, and as part of a MR filling it in would go a long way. The changelog might also help in figuring out when to make a release (major or minor).
I probably missed out some things to consider, suggestions are welcome!!!