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.24”, consistent with the existing tracks for earlier feature releases. See previous comments above for the strategy and agreement on this usage of tracks.
Regular release time again. 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.25”, consistent with the existing tracks for earlier feature releases. See previous comments above for the strategy and agreement on this usage of tracks.
Regular release time again. 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.26”, consistent with the existing tracks for earlier feature releases. See previous comments above for the strategy and agreement on this usage of tracks.
Regular release time again. Can a new track please be created for the next CMake feature release series, which will shortly begin its next release candidate phase. The track name should be “3.27”, consistent with the existing tracks for earlier feature releases. See previous comments above for the strategy and agreement on this usage of tracks.
Regular release time again. Can a new track please be created for the next CMake feature release series, which will shortly begin its next release candidate phase. The track name should be “3.28”, consistent with the existing tracks for earlier feature releases. See previous comments above for the strategy and agreement on this usage of tracks.
Regular release time again. Can a new track please be created for the next CMake feature release series, which starts its next release candidate phase today. The track name should be “3.29”, consistent with the existing tracks for earlier feature releases. See previous comments above for the strategy and agreement on this usage of tracks.
Regular release time once again. Can a new track please be created for the next CMake feature release series, which starts its next release candidate phase today. The track name should be “3.30”, consistent with the existing tracks for earlier feature releases. See previous comments above for the strategy and agreement on this usage of tracks.
It looks like there has been a change recently to allow snap maintainers to add their own tracks. I’ve made a request for setting up the TCG for the cmake snap to enable that in future, but for now, could you please still create the 3.30 track to avoid further delay so I can push out the package for the CMake 3.30 release made today.
I must be missing something. Track Creation Guardrails have been set up for the cmake snap. I am unable to find anywhere I can now create new tracks, so I tried publishing to a new (not yet existing) track, and of course that fails. What do I have to do now to create a new track? I need a new 3.31 track for the next feature release, but I don’t see how I can self-service that like I expected to be able to. I’ve been unable to find any docs about how to do this now.
I just had another look at my other snaps without a guardrail set. Where before they showed “Add Track” that didn’t work, now it’s:
So my guess here is it’ll just need someone to look at it from the backend side. As a user, unless something extreme is interfering like an adblocker, you should just be able to see it, at least one of the two, whereas currently you get neither.