hm, that belongs in
latest/edge and we consistently steer people requesting e.g. “nightly” or “from-master” tracks into using
latest/edge for this.
Sorry It’s not possible to rename tracks.
We can create a 26.2 track and a suitable build of emacs can be published to it (if I understand correctly, you would publish what’s currently in
26.2, but people who are tracking
latest and want to drop back to 26.2 (meaning, not following
latest to get updates as they happen) would need to do so explicitly, which is how tracks are designed to work.
I have to say I find it very strange for a text editor to need tracks; wouldn’t most people welcome a new version of emacs and want to upgrade to it? Does it frequently include backward-incompatible changes in stable releases? (example: My editor is installed from deb packages and I have no idea when it updated from 7.x to 8.x - nothing stopped working or required me to take any action.).
I went checking https://www.gnu.org/savannah-checkouts/gnu/emacs/emacs.html#Releases and the versioning scheme doesn’t tell me much about the release cadence (if any) and how a version’s compatibility with others is reflected in the version number; 26.2 and 26.1 say they have a “wide variety of new features” (none of the highlighted ones seem to me like they’d warrant a track for people to choose to stay on 26.1 explicitly, for instance) or are security or bug fix releases.
Given the above, I have to say I’m -1 to both track requests
Let’s start the 7-day comment period for other reviewers to chime in as well; remember not only my vote counts.