Track request: new 1.4 track for ldc2 snap package

[roadmr]

Hello again!

The process outlined here applies to track requests as well, (see the first post only). This allows reviewers and architects to chime in on the request.

Process for aliases, auto-connections and tracks

Definitions Reviewers are in the @reviewers forum group Architects are those responsible for the design of snapd. Votes are in favor (+1), against (-1), abstain (+0) Voting period is one week Voting period extension is 3 days Process Requester creates a forum post in the store-requests category and makes case for change. To disambiguate snaps, the requester should either give the store URL for the snap or give the name and publisher of the snap. Voting period starts at time of request. Reques…

Per that process, could you please provide the store URLs or mention the publisher and snap name for your snap if it already exists? (if not, just mention it so we can consider whether to pre-create the tracks).

Also, as with the dmd track request, could you explain the need for tracks for this new version? While this sounds more clear-cut than dmd (since ldc2 has 1.3 and 1.4 releases), this information will help in making the decision. Remember tracks are meant to allow users to receive updates to an earlier release of the software, on which they need to stay because of data incompatibility or other reasons.

Thanks!

• Daniel