Hi!
We’d like to request a new track for the ignite snap. This track would be called 28/v28. Looking at other topics, I found those questions that I will already answer here:
- What are the snap’s release cadence? How often is a new major version (potentially requiring a new track) released? Is this documented somewhere by upstream?
We publish the snap at each patch version. We have just released a major version (v29) that we have updated to the latest track. However we’d like people to still be able to install v28. This is because a major version in Ignite means updating the blockchain to a higher version of the Cosmos SDK / IBC for all functionalities to work smoothly. Major versions are created approximately once a year or every two years.
- Is there some commitment from upstream on maintenance of old versions? Will older versions be supported when newer versions are created?
Our maintenance policy derives of the SDK maintenance policy. Meaning we support the last two released version of Ignite. Meaning, as of today v29 and v28 are supported. v28 is no more supported once v30 is released (in about a year or two).
- Are new versions backwards-incompatible? meaning, if I was running non-DEV and try to install DEV, will that just work, or do I need to migrate my data/configuration, or will things break horribly?
We strive for the most backward compatibility where we can, but the scaffolding logic breaks between major versions (due to the Cosmos Stack template being updated). However, no config modification of the tool itself is required. When this happens, we have an ignite doctor command that resolves the issues.