As regulars here will know, Simutrans-Experimental, as it is now called, is often confused for a testing build of new features for Simutrans-Standard, whereas it is in fact a fork with a different feature-set intended to provide more realism. The name "Simutrans-Experimental" originally came from when I first started work on this project back in 2008 and did not know what would become of it (the idea originally was for the features to be implemented into what was then termed "the trunk").
As many may recall, there was a discussion some time ago about renaming Simutrans-Experimental to Simutrans-Extended to reflect the real status of the project. Several people had then recommended doing so as soon as possible. I did not take action on this at the time because the official release builds, from the now old 11.x line, were still named internally "Simutrans-Experimental".
However, now that I have a nightly build setup for both Windows and Linux, this seems as though it would be a good time to make the transition, and deprecate the old 11.x release builds (although I will still keep them available in case anybody wants to use the older executables; I believe that Carl Baker was using these until recently at least).
The popularity of early access development and the interest that people have shown in playing the latest, in-development builds over the last few years, it seems sensible to me officially to deprecate the releases and point new users towards the nightly builds with the caveat that these are still work in progress.
In fact, even the old 11.x builds had bugs and gameplay issues and the current builds are in many ways more stable and complete than the older builds. It does not seem to me to be sensible to release a new release build until I have completed at least the first pass at pakset balancing, which can only be done once a number of balance critical features are implemented, which will take some considerable work. It is evident that people would like to play the updated version in the meantime.
Doing this now will have a number of advantages, including familiarising people with the new name, the ability to use the updated name explicitly in videos (there is not much point now in adding commentary referring to "Simutrans-Experimental" knowing that the name is due to change), and setting up social media accounts with the new name.
Before I actually make the changes that I need to make (including renaming inside the code), I should be grateful for any feedback that anyone might have as to any possible transitional issues in respect of this that I might not have considered, as well as views from those who administer these forums about the practicalities of renaming the "Simutrans-Experimental" subforums to be "Simutrans-Extended" subforums.
Edit: Another thing to consider is the use of Github branches. I have just accidentally (I am not quite sure how this happened, actually) pushed the road-vehicle-rescaling branch of the pakset to the master branch, which was supposed to represent the latest pre-half heights code. Prissi mentioned recently that it was confusing that the master branch of the code on Github was so out of date.
Might it be sensible to start using the master branches for the official nightly builds, and create sub-branches from that especially for release candidates and release final versions in the future?