This means that all components of the SDK (i.e. DartVM, dart2js, dartanalyzer,
pub) will have the same semantic version string when invoking them with
'--version'. The version string is also present in "dart-sdk/version".
The editor will have an eclipse compatible version which consists of
major.minor.patch.qualifier.
The SDK versions look like this on our three channels:
- bleeding-edge: 1.1.0-edge.30857
- dev: 1.1.0-dev.2.42
- stable: 1.1.0
The SDK versions comply with the semantic versioning standard, see:
http://semver.org/.
The DartEditor versions look like this on our three channels:
- bleeding-edge: 1.1.0.edge_030857
- dev: 1.1.0.dev_02_42
- stable: 1.1.0.release
The DartEditor versions comply with semantic eclipse versioning scheme.
(The leading zeros are necessary due to lexicographic ordering.)
From both version schemes, it becomes clear on which channel a user is on.
R=danrubel@google.com, kasperl@google.com, rnystrom@google.com
Review URL: https://codereview.chromium.org//104403005
git-svn-id: https://dart.googlecode.com/svn/branches/bleeding_edge/dart@30905 260f80e4-7a28-3924-810f-c04153c831b5
A few general notes:
We always generate an installer that will do a full upgrade, i.e., uninstall the old installer and reinstall the new one.
We need wix 3.6 or above, I will add a dependency for this to our bot that will run this. For local testing you can either put wix in your path or pass in the location
We use * for both product id and component component guids (i.e., wix will generate them on the fly. Since we don't track files across versions and we always do a full update this is fine. If we want to change to patch releases we need to change that functionality.
Review URL: https://chromiumcodereview.appspot.com//43273003
git-svn-id: https://dart.googlecode.com/svn/branches/bleeding_edge/dart@29348 260f80e4-7a28-3924-810f-c04153c831b5
kustermann@google.com