Can we potentially discuss abandoning the even/odd versioning scheme especially with the move to Slicer 6 development beginning? It appears that the Linux kernel used to do this and GNOME used to do this, but not anymore. It would be clearer to then have a GitHub milestone for “6.0” containing all the issues planned for the Slicer 6.0 release, rather than having a Slicer “5.13” milestone. Similarly having both a Slicer 5.11 and 5.12 milestone was confusing as it was difficult to know are issues in the 5.11 milestone for the 5.12 release, or are the issues in the 5.12 milestone for the 5.12 release. In general the milestone version is detailing all the issues to complete prior to the stable release of that version.
There has been confusion regarding this even/odd convention for stable releases including most recently as indicated by the following post below, but even by the people I work with as well.