Releasing

Creating a new release

From IntelliJ:

• ensure that the changelog in resources/META-INF/plugin.xml is up-to-date (from the current milestone)
  • edit plugin.xml.template: update version number, release notes
  • run ant plugin.xml in a terminal emulator to update plugin.xml
• commit these changes
• create a new branch locally from that commit (git checkout -B release_<version> SHA, replacing <version> and SHA as appropriate)
• in a terminal emulator, bin/plugin --release=<version> build, again replacing <version with the current version number
• the plugin is created as three separate flutter-studio.zip products in /project/root/artifacts/release_<version> (all three will be uploaded separately)
  • 3.0
  • 2017.2
  • 2017.3
• push your release branch upstream (git push -u upstream release_20.0)

From github:

• go to https://github.com/flutter/flutter-intellij/releases
• select Draft a new release
• enter a version tag and release title of x.y.z (e.g., 20.0); be sure and target your release branch (e.g., release_20.0)

From plugins.jetbrains.com:

• sign into https://plugins.jetbrains.com
• from https://plugins.jetbrains.com/plugin/9212?pr=idea, select 'update plugin'
• upload the flutter-studio.zip files (one for each product) created from the earlier step (note: the .zip file)

Pushing a patch to an existing release

When it's necessary to patch a previously released build:

Create a branch

• the fix should have already been committed to master
• look at the releases page and get the git commit of the release to patch
• create a new branch locally from that commit (git branch release_15.0 4324f80)
• change to that branch (git checkout release_15.0)

Cherry-pick the fix

• cherrypick the specific commit (git cherry-pick 2d8ac6a)
• rev the plugin numbers (append .1 to the plugin version in resources/META-INF/plugin.xml)
  • See details on editing under "Creating a new release", above
• commit your version change and push the new branch up to the repo
  • if on a fork of the main repo, please make sure to push to the main repo: git push upstream release_15.0
  • if the branch already exists on the upstream repo, use git checkout -b release_15.0 upstream/release_15.0 to get a local copy

Re-deploy the new Jar

• build a new version of the jar file (run build-all.sh as described above)
• sign into https://plugins.jetbrains.com
• from https://plugins.jetbrains.com/plugin/9212?pr=idea, select 'update plugin'
• upload the flutter-studio.zip created from the earlier step (note: the .zip file)