You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Tag the build (brackets, brackets-shell) using release-1.0 format (Creating 'Release' in brackets tags the build, so only need to do this in brackets-shell?)
Announcement to the brackets-dev group for this release and work in the new cycle
Merge localizations/other release changes back into master
Merge localizations/other release changes to brackets-shell master
Change the health URL to health.brackets.io in the RELEASE branch.
Create a bundle with the Extract extension
Create a new release on github.com/adobe/brackets/releases
Rename and post all 4 platform Builds to github.com/adobe/brackets/releases page
Publish the release on github.com/adobe/brackets/releases
Update Health Data Wiki with the new data that we are sending to the server.
Update build number & date in brackets-updates repo AND push Brackets update notifications to brackets.io (for ALL 5 locales)
Verify posted builds Mac
Verify posted builds Windows
Verify posted builds Linux 64
Verify posted builds Linux 32
Post Blog post
Double-check brackets.io home page to make sure button and new features list look right
Verify that update notifications work from an older build
Issue by nethip
Thursday Apr 28, 2016 at 05:30 GMT
Originally opened as adobe/brackets#12388
Tasks to deploy a release publicly
release-1.0
format (Creating 'Release' in brackets tags the build, so only need to do this in brackets-shell?)Create a bundle with the Extract extension@
ingorichter Post announcement in brackets-announce@
pthiess Gather cycle times from "Ship It!” columnThe text was updated successfully, but these errors were encountered: