Per Process for aliases, auto-connections and tracks we need to gather votes from reviewers and tally them at the end of the one-week waiting period.
I see currently network-manager is at 1.2 on latest. SO your plan is to keep 1.2 on latest for the time being and start publishing 1.10 to its track?
Are you happy with people who start tracking the 1.10 track to need manual action to move out of 1.10? that is - people who are currently on latest will magically move from 1.2 to 1.10 when the latter is pushed to latest. But people who opt in to the 1.10 track will NOT automatically move to e.g. 1.30 when that is released in latest or in a putative 1.30 track (unless you do something horrid like publishing 1.30 to the 1.10 track as well).
Just mentioning this to ensure the characteristics of tracks (mainly their stickiness and need of manual intervention to ever move off the track) are taken into account and we don’t get network-manager in a tangle.