diff --git a/docs/ReleaseInstructions.md b/docs/ReleaseInstructions.md index b027be31..ea2711c6 100644 --- a/docs/ReleaseInstructions.md +++ b/docs/ReleaseInstructions.md @@ -21,10 +21,14 @@ The above steps can be done on a fork and committed via a pull request. 1. Ensure you are on the `master` branch with `git checkout master`. 1. Switch to the `gh-pages` branch with `git checkout gh-pages`. -1. Copy the `svg-edit-X.Y` directory to `releases/svg-edit-X.Y`. -1. Commit these changes with `git commit -m "Updating binary files for release X.Y"`. +1. Copy the `svg-edit-X.Y` directory to `releases/svg-edit-X.Y` (minus + `.git` and `.gitignore` and including the working built + `svgedit-config-es.js` and `svgedit-config-iife.js` files). +1. Commit these changes with `git commit -m "Updating files for release X.Y"`. 1. Switch back to the `master` branch with `git checkout master`. 1. Ensure this step worked by visiting + (and in an ES6-Module-compliant browser, + ) The above steps can be done on a fork and committed via a pull request. @@ -33,9 +37,10 @@ The above steps can be done on a fork and committed via a pull request. 4. Attach the `svg-edit-X.Y-src.tar.gz` and `build/svg-edit-X.Y.zip` files to the release. --> 1. Go to and select `Draft a new release`. -1. Make the release target point at the commit where the makefile and changes were updated. +1. Make the release target point at the commit where the changes were updated. 1. Write a short description of the release and include a link to the live version: - + . + See the previous releases for the format. 1. Create the release! You will need to be a member of the SVG-Edit GitHub group to do this step.