Versioned Channels

[ciscorucinski]

So far, the snap points to the latest version. Even the future parallel installs (#26) will do that, but AS Previews should only point to the latest. Would it be a good idea to also create version specific names?

I notice that when I go back to older projects, I cannot get them running due to the non-backward compatibility. I will get errors after errors until it can finally run (if I can get it to run). That's because each AS version will place restrictions on minimum versions of dependencies like Gradle and the Android Gradle Plugin.

If I can run a previous version on Android Studio, then the problem can be reduced significantly.

Also, this would line it up with IntelliJ IDEA Community Snap's versioned channels (https://snapcraft.io/intellij-idea-community).

Versions - Stable

v3.3/stable
v3.2/stable
v3.1/stable
v3.0/stable
...

[ciscorucinski]

It might be a good idea to include Preview versions inside the of the base android-studio Snap only in the versioned channels. You would have to specify the edge or beta risk level.

The android-studio Snap is for stable releases, but this would also help to show the activity of the snap to new users, and will allow easier switching between channels for quick testing

Versions - Possible

v3.5/edge
    // Currently in Canary
    // only 'sudo snap install android-studio --channel=v3.5/edge --classic'

v3.4/beta
    // Currently in Beta. Maybe RC later?
    // Only 'sudo snap install android-studio --channel=v3.4/beta --classic'

[patricks-dev]

Another use case in favor of channels:

I'm using Lombok to speed up development. However, most of the time I gain from using it is lost trying to resolve compatibility issues between versions of Android Studio and the Lombok plugin.

Any mechanism that would enable be to downgrade Android Studio would be greatly appreciated!