From here on out, I’ll have two current packages of Inform 6 for Unix out at a time. One is pegged to 6.35 (stable) and the other follows 6.36 (development). Once 6.36 is finalized, that’ll become the “stable” release and 6.37 becomes “development”.
If you like, you can install both at the same time. To do this, install what you want as the default first. Then for the alternative, do make install-alt. Remember to do make submodules when you switch between stable and development.
I’ll have a 6.36dev package available in a few days.
Is there a tag or branch I should follow to only get the stable versions from git via https://gitlab.com/DavidGriffith/inform6unix? I have a build system that semi-automatically refreshes the compiler and punyinform tree from that repository, and it would be nice to switch to one that can track stable if that’s possible.
The current stable branch is 6.35. Version 6.35 Revision 5 and later will appear there. The master branch follows the development release of the Inform 6 Compiler, whichever version that is. When 6.36 is finalized, I’ll make a 6.36 branch which will then become stable. Unfortunately, Git doesn’t allow for multiple names for a single branch.
There is no branch named stable because Git doesn’t allow a branch to have more than one name. Thinking more on this, I could rework the repo to have a dev branch and reserve the master branch as the stable one. That seems more sensible and it’s early enough for this change to not be disruptive.
Yeah, you can always just keep a separate stable branch and fast-forward merge in changes from 6.35 now, then merge 6.36 when that’s stable, etc. I think the frustrating thing people run into more often here is the immutability of tags (which I only just learned can be deleted!).
But I think that keeping a separate development branch for the latest dev version and keeping your default branch stable suits my use case perfectly, and provides the least surprise.
But all that said, it’s your repo and you’re the one doing the work, so whatever feels most comfortable for your workflow is important!