zcy
/
svgedit
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Update instructions to use binary attachments 

Instead of storing compressed zip and tar.gz files on gh-pages, just link directly to them from the releases page (https://github.com/progers/svgedit/releases).
master
Philip Rogers 2015-11-24 18:41:38 -08:00
parent 2bdc24ff57
commit f6005d6ac5
1 changed files with 6 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
docs/ReleaseInstructions.md
View File

@ -13,13 +13,12 @@ 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. Ensure you are on the `master` branch with `git checkout master`.
2. From the root directory run `make`. 2. From the root directory run `make`.
3. Copy `build/svg-edit-X.Y/`, `build/svg-edit-X.Y.tar.gz`, and `build/svg-edit-X.Y.zip` to a temporary directory. 3. Copy `build/svg-edit-X.Y/`, `build/svg-edit-X.Y-src.tar.gz`, and `build/svg-edit-X.Y.zip` to a temporary directory.
4. Switch to the `gh-pages` branch with `git checkout gh-pages`. 4. Switch to the `gh-pages` branch with `git checkout gh-pages`.
5. Copy the `svg-edit-X.Y` directory to `releases/svg-edit-X.Y`. 5. Copy the `svg-edit-X.Y` directory to `releases/svg-edit-X.Y`.
6. Copy `svg-edit-X.Y.tar.gz` and `svg-edit-X.Y.zip` to `compressed/svg-edit-X.Y.tar.gz` and `compressed/svg-edit-X.Y.zip`. 6. Commit these changes with `git commit -m "Updating binary files for release X.Y"`.
7. Commit these changes with `git commit -m "Updating binary files for release X.Y"`. 7. Switch back to the `master` branch with `git checkout master`.
8. Switch back to the `master` branch with `git checkout master`. 8. Ensure this step worked by visiting https://svgedit.github.io/svgedit/releases/svg-edit-X.Y/svg-editor.html
9. Ensure this step worked by visiting https://svgedit.github.io/svgedit/releases/svg-edit-X.Y/svg-editor.html
The above steps can be done on a fork and committed via a pull request. The above steps can be done on a fork and committed via a pull request.
@ -29,11 +28,11 @@ The above steps can be done on a fork and committed via a pull request.
2. Make the release target point at the commit where the makefile and changes were updated. 2. Make the release target point at the commit where the makefile and changes were updated.
3. Write a short description of the release and include a link to the live version: 3. Write a short description of the release and include a link to the live version:
https://svgedit.github.io/svgedit/releases/svg-edit-X.Y/svg-editor.html https://svgedit.github.io/svgedit/releases/svg-edit-X.Y/svg-editor.html
4. Attach the `svg-edit-X.Y.zip` and `compressed/svg-edit-X.Y.tar.gz` files to the release. 4. Attach the `svg-edit-X.Y-src.tar.gz` and `build/svg-edit-X.Y.zip` files to the release.
5. Create the release! 5. Create the release!
You will need to be a member of the SVGEdit GitHub group to do this step. You will need to be a member of the SVGEdit GitHub group to do this step.
## Update the project docs ## Update the project docs
Update `README.md` and add a reference to your shiny new release. Update `README.md` with references and links to the shiny new release.