@roadmr ah, it seems like the track request process has got more formal since the last time I had to request any
Per that process, could you please provide the store URLs or mention the publisher and snap name for your snap if it already exists?
Could you explain the need for tracks for those two very similar-looking versions?
In a similar manner to the Go snap, I’m planning on having one track per minor release of the
dmd compiler (as is already done for the
ldc2 snap I referred to in a different post).
The reason for two tracks is that 2.074 should provide long-term support for the 2.074.x dmd release series (first released 10 April 2017, which the current snap is built from) and the upcoming 2.075.x release series (which should come out shortly, probably in early August).
If you go through the release history here: https://github.com/dlang/dmd/releases you should be able to see that there’s a time period of about 3 months between minor releases of dmd (i.e. 2.071.0, 2.072.0, 2.073.0, 2.074.0, etc.).
The fact that there is an upcoming new minor release (2.075.0) is what motivates the request for tracks, since up until now there was no need to support any earlier versions.
I wonder how necessary a track would be: do people using 2.074 really need to stay on that version or can they go to 2.075 without needing to rewrite their code?
Generally speaking where DMD is concerned, one can’t exclude breaking changes between releases. So there are definitely use-cases for staying on an earlier version.
Does that give you everything you need?
Thanks & best wishes,