I’ve developed a new Emmet plugin for some time and I’d like to to release it for all users. Since this is one of the most downloaded plugin for Sublime Text, I’d like to take advices from developers for the best upgrade strategy.
So far I have:
- A new plugin repo.
- A build step on CI, mostly used to download a single dependency (py-emmet) from PyPI. Build step then creates artifact with full plugin.
- Tag-based release instead commit-based in old plugin: I’d like to inform users that new version is available and it provides new developer experience.
According to Package Control docs, switching repos should be an easy step. My main concern is a build step: I think Package Control will download source code for tag instead of artifact?
Also, if I switch to tag-based release, will Package Control show message for new release (defined in
Any advices on how to make it as smooth as possible for end-users?