Kronuz/SublimeCodeIntel — pull request #73 by wbond (2011-12-24 21:21:38+00:00)
Title: Package Control Fixes

I noticed you had a package-metadata.json file in the repo with a specific version number. Package Control actually overwrites this information when it installs a package, primarily so that GitHub maintainers do not have to maintain the file.

If you do want to control the version number, you just need a custom packages.json file with the metadata about the package and the download URL. I've provided one based on your v1.3 commit. When you are ready to make a new release, just update the version number and the hash in the URL and users will get the upgrade. This will also help in that users won't get potentially untested commits between releases, like they do now.

One thing of note, up until version 1.3.1 of Package Control, date-versioned packages (based on commit dates) would always end up being higher than manual versions since 2011 > 1.*. I've fixed this with 1.3.1 where date-based version a prefixed with a 0 when doing a comparison, allowing developers such as you do change from implicit versioning to explicit versioning.

The other thing you might find useful with Package Control is the messaging system. You can set up messages to be shown to users on install and upgrade. You can see an example at https://github.com/wbond/sublime_alignment/blob/master/messages.json and the docs are at http://wbond.net/sublime_packages/package_control/package_developers#Installation_and_Upgrade_Messages.