Permalink
Browse files

Minor updates to the checklist used to release new versions

  • Loading branch information...
1 parent 539b60b commit 11d86e56da009f7a5728fff36db394d9256e6461 @javiereguiluz committed Oct 9, 2016
Showing with 8 additions and 7 deletions.
  1. +8 −7 .github/RELEASE_CHECKLIST.md
@@ -6,18 +6,19 @@ How to release a new EasyAdmin version
stable release. Example: change `1.12.6-DEV` to `1.12.6`
2. Update the version number in the `README.md` link that points to the stable
version documentation. Example: change `1.12.5` to `1.12.6`
-3. Compile the CSS and JavaScript assets using the `compile_assets.sh` script
- provided in `Resources/bin/`
-4. Create the tag and sign it. Example: `git tag -s v1.12.6` (the tag version is
+3. Commit and push the two previous changes.
+4. Execute the `Resources/bin/compile_assets.sh` script to compile the CSS and
+ JavaScript assets. If there are any changes, commit and push them.
+5. Create the tag and sign it. Example: `git tag -s v1.12.6` (the tag version is
always prefixed with `v`, but remove it for the tag comment: `1.12.6`).
-5. Push the tag to GitHub. Example: `git push origin v1.12.6`
-6. Prepare the changelog of the new version with the custom `changelog` Git
+6. Push the tag to GitHub. Example: `git push origin v1.12.6`
+7. Prepare the changelog of the new version with the custom `changelog` Git
command. Example: `git changelog v1.12.5` (the version passed to the command
is the previous version used as a reference to list the changes).
-7. Go to https://github.com/javiereguiluz/EasyAdminBundle/releases and click
+8. Go to https://github.com/javiereguiluz/EasyAdminBundle/releases and click
on `Draft a new release`. Select the tag pushed before and paste the
changelog contents.
-8. Update again the value of the `EasyAdminBundle::VERSION` constant to start
+9. Update again the value of the `EasyAdminBundle::VERSION` constant to start
the development of the next version. Example: change `1.12.6` to `1.12.7-DEV`
Resources

0 comments on commit 11d86e5

Please sign in to comment.