{"_id":"54c905e44574700d00f01679","category":{"_id":"54c8f8ae0174630d00efa874","pages":["54c9056a7a11f60d0022a867","54c905914574700d00f01677","54c905c70174630d00efa89e","54c905e44574700d00f01679","54c906014574700d00f0167b"],"version":"547cd7662eaee50800ed108c","__v":5,"project":"547cd7662eaee50800ed1089","sync":{"url":"","isSync":false},"reference":false,"createdAt":"2015-01-28T14:56:46.281Z","from_sync":false,"order":2,"slug":"sell","title":"Sell"},"parentDoc":null,"project":"547cd7662eaee50800ed1089","user":"547cd6ac78fd57080023ca99","version":{"_id":"547cd7662eaee50800ed108c","project":"547cd7662eaee50800ed1089","__v":9,"createdAt":"2014-12-01T21:02:30.851Z","releaseDate":"2014-12-01T21:02:30.851Z","categories":["547cd7672eaee50800ed108d","54c8f8ae0174630d00efa874","54c8f8bd7a11f60d0022a832","54c8f8c60174630d00efa876","54c8f8f10174630d00efa877","55155826bc466623002afe83","551558324c7c1e39003735a0","56052058e266000d008971c7","57909a453b845d0e006a37d5"],"is_deprecated":false,"is_hidden":false,"is_beta":false,"is_stable":false,"codename":"","version_clean":"1.0.0","version":"1.0"},"__v":16,"updates":["554a0d6bb9fb933900cc749f"],"next":{"pages":[],"description":""},"createdAt":"2015-01-28T15:53:08.489Z","link_external":false,"link_url":"","githubsync":"","sync_unique":"","hidden":false,"api":{"results":{"codes":[]},"settings":"","auth":"required","params":[],"url":""},"isReference":false,"order":3,"body":"After your application is ready for its big journey, you need to publish it in _Application > Release Management_ section.\n\nYou will be able to upload an application to DevMate only if you have set up [DevMateKit Updates](doc:updates)! That was done to prevent occasional and inappropriate uploads to DevMate.\n\nAfter clicking on **Add new application version** you will be able to set up your release with the following options:\n\n*   Status\n\n    *   Draft – your application and any info about it will not be published anywhere\n    *   Testing – you will be able to test how updates work. Learn how [to enable test mode](http://devmate.readme.io/v1.0/docs/updates#test-updates-integration) in your application\n    *   Live – current version that will be available for download and updates.\n\n*   Bundle version – specify version numbers like in `CFBundleVersion` in _info.plist_ file\n*   Release files – you can download installation files in .zip or .dmg format and zipped .dSYM file. You can learn more about symbolication from [Apple documentation](https://developer.apple.com/library/ios/technotes/tn2151/_index.html)\n*   Release notes – use Markdown for text formatting. You can add localized release notes. You can add an HTML code to the release notes, for instance, you can advertise your other app or add some greeting to your customers. Keep in mind, that due to ATS (App Transport Security) restrictions in OS X El Capitan all links that you use in your HTML code, including links to images, should be `https://`, otherwise, they won’t work in an update window.\n\nYou can add more detailed options by clicking on **Advanced**.\n\n*   Short bundle version – as it will be displayed to your customers and as specified in `CFBundleShortVersionString` *info.plist* key.\n*   Version codename – will be visible in DevMate only\n*   Release date – just for your reference. Your release will not be published automatically.\n*   OS limitation – here you can specify the eldest OS X version supported. Customers who use elder version will not be updated to this application version\n*   Update method – here you can set a specific link with the update conditions. For example, if you want to charge an extra fee for the update, you need to inform your customers about that. So you can select *'External update'* procedure and enter the link to update rules.\n[block:html]\n{\n  \"html\": \"<iframe src=\\\"https://player.vimeo.com/video/123944209?title=0&byline=0&portrait=0\\\" width=\\\"750\\\" height=\\\"600\\\" frameborder=\\\"0\\\" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>\"\n}\n[/block]\n\nPlease note that after making live a new application version, the previous one will be marked as _Archive_. You can set _Archive_ versions _Online_ or _Offline_, making them still available or unavailable for download.","excerpt":"","slug":"manage-versions","type":"basic","title":"Manage Versions"}
After your application is ready for its big journey, you need to publish it in _Application > Release Management_ section. You will be able to upload an application to DevMate only if you have set up [DevMateKit Updates](doc:updates)! That was done to prevent occasional and inappropriate uploads to DevMate. After clicking on **Add new application version** you will be able to set up your release with the following options: * Status * Draft – your application and any info about it will not be published anywhere * Testing – you will be able to test how updates work. Learn how [to enable test mode](http://devmate.readme.io/v1.0/docs/updates#test-updates-integration) in your application * Live – current version that will be available for download and updates. * Bundle version – specify version numbers like in `CFBundleVersion` in _info.plist_ file * Release files – you can download installation files in .zip or .dmg format and zipped .dSYM file. You can learn more about symbolication from [Apple documentation](https://developer.apple.com/library/ios/technotes/tn2151/_index.html) * Release notes – use Markdown for text formatting. You can add localized release notes. You can add an HTML code to the release notes, for instance, you can advertise your other app or add some greeting to your customers. Keep in mind, that due to ATS (App Transport Security) restrictions in OS X El Capitan all links that you use in your HTML code, including links to images, should be `https://`, otherwise, they won’t work in an update window. You can add more detailed options by clicking on **Advanced**. * Short bundle version – as it will be displayed to your customers and as specified in `CFBundleShortVersionString` *info.plist* key. * Version codename – will be visible in DevMate only * Release date – just for your reference. Your release will not be published automatically. * OS limitation – here you can specify the eldest OS X version supported. Customers who use elder version will not be updated to this application version * Update method – here you can set a specific link with the update conditions. For example, if you want to charge an extra fee for the update, you need to inform your customers about that. So you can select *'External update'* procedure and enter the link to update rules. [block:html] { "html": "<iframe src=\"https://player.vimeo.com/video/123944209?title=0&byline=0&portrait=0\" width=\"750\" height=\"600\" frameborder=\"0\" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>" } [/block] Please note that after making live a new application version, the previous one will be marked as _Archive_. You can set _Archive_ versions _Online_ or _Offline_, making them still available or unavailable for download.