Per Process for reviewing aliases, auto-connections and track requests we need votes from reviewers/architects before creating these tracks.
What’s your intended use of tracks for this? will you keep a development version on the “latest” track and “track off” to e.g. artful, etc. once the snap is “frozen” for that specific Ubuntu release? Are you planning to do such an operation before said Ubuntu release is actually released?
That’d be an argument for naming it “artful” instead of “17.10” (what if artful delays to 17.11 and the track name becomes misleading? heh).
Personally I would keep e.g. development stuff on latest/(beta,edge) and frozen/close-to-freeze stuff on latest/(stable,candidate) and only split into a track once the corresponding Ubuntu version is released (say, making what’s in latest/stable go to 17.10/stable) but it’s just a thought. If “by codename” semantics match your use case, I’m +1 as we have precedent of naming tracks after codenames, a clear example being openstack.