CMake follows releases numbered like 3.14.5 where 3.14 would be a feature release and 3.14.5 would be a patch release. The latest official release is 3.14.5 and the 3.15 series is currently in release candidate stage. I’d like to request tracks be created with the following names:
3.14
3.15
CMake also has a nightly build and it would be good to have a separate track for those too. Could the following track also please be approved to capture that:
nightly
I will eventually look into creating another track for master builds, but for now, the above three tracks should be enough for me to get the important releases and builds covered.
Actually, don’t worry about creating the “nightly” track. I may not be able to easily implement what I had intended for that one, so let’s defer it. The 3.14 and 3.15 tracks are definitely needed though.
I spoke to @crascit in person to clarify the usual questions when tracks like this are requested:
Cmake has 3 releases per year so the release cadence is great for use of tracks.
Though Cmake strives for backwards compatibility, users can and do choose to use an older release for stability reasons, which is a valid use case for tracks.
I have created the above tracks, since we were able to fast-track the process of discussing this with the developers, we have at least 4 snap reviewers here at the Snapcraft Summit, and the CMake use case is a good match for use of tracks.
(Requesting this here so the context with previous tracks is preserved. Let me know if you prefer a new request for these tracks instead.)
Can a new track please be created for the next upcoming CMake feature release series (likely to start in a month or so). The track name should be “3.16”, consistent with the existing 3.14 and 3.15 tracks. See previous comments above for the strategy and agreement on this usage of tracks.
Can a new track please be created for the next CMake feature release series, which started today. The track name should be “3.17”, consistent with the existing tracks for earlier feature releases. See previous comments above for the strategy and agreement on this usage of tracks.
Can a new track please be created for the next CMake feature release series, which is expected to start soon. The track name should be “3.18”, consistent with the existing tracks for earlier feature releases. See previous comments above for the strategy and agreement on this usage of tracks.
Can a new track please be created for the next CMake feature release series, which has just begun its next release candidate phase. The track name should be “3.19”, consistent with the existing tracks for earlier feature releases. See previous comments above for the strategy and agreement on this usage of tracks.
Can a new track please be created for the next CMake feature release series, which is about to begin its next release candidate phase. The track name should be “3.20”, consistent with the existing tracks for earlier feature releases. See previous comments above for the strategy and agreement on this usage of tracks.
Can a new track please be created for the next CMake feature release series, which will begin its next release candidate phase soon. The track name should be “3.21”, consistent with the existing tracks for earlier feature releases. See previous comments above for the strategy and agreement on this usage of tracks.
Can a new track please be created for the next CMake feature release series, which will begin its next release candidate phase shortly. The track name should be “3.22”, consistent with the existing tracks for earlier feature releases. See previous comments above for the strategy and agreement on this usage of tracks.
Can a new track please be created for the next CMake feature release series, which will begin its next release candidate phase shortly. The track name should be “3.23”, consistent with the existing tracks for earlier feature releases. See previous comments above for the strategy and agreement on this usage of tracks.
from me. 