Track request for influxdb and influx snaps

I’d like to request tracks named 2.0 for both the influxdb and influx snaps. This will be used to publish release in the 2.0 series so we can offer multiple supported releases at a time.

1 Like


First-time track requests follow Process for aliases, auto-connections and tracks , meaning we will have a 7-day waiting period to allow for reviewers to inspect the request and cast their votes.

The main criteria for tracks is backward-incompatibility between releases of your software, particularly if people do have a legitimate reason to want to choose an older version over the new one.

For example, if it involves invasive code changes, or has a different data format, and there’s no easy migration/conversion tool that people could use with a new release.

Can you please indicate whether this is the case with your software?

Another thing we ask for is a reasonable lifetime for releases. If you’re releasing an incompatible version every 2 weeks, tracks would be a poor fit as you would be stranding a lot of people on older releases as you move ahead. This typically indicates your software is still evolving and tracks are really best suited for mature, stable projects.

If you have a link or documentation to your project’s release schedule/cadence, that will be useful for reviewers.

Thanks and apologies for asking so many questions :slight_smile:

  • Daniel