X-Git-Url: https://git.immae.eu/?a=blobdiff_plain;f=RELEASE_PROCESS.md;h=881f07710e5c8557f47a9e559f04dae477245af7;hb=HEAD;hp=627bd844caf619e6dbdf5e86d1b61df7b66b228f;hpb=edc8bc0b2f23bf27ac33b9de079644cc9076579a;p=github%2Fwallabag%2Fwallabag.git diff --git a/RELEASE_PROCESS.md b/RELEASE_PROCESS.md index 627bd844..881f0771 100644 --- a/RELEASE_PROCESS.md +++ b/RELEASE_PROCESS.md @@ -4,61 +4,60 @@ A release is mostly a git tag of http://github.com/wallabag/wallabag, following ### Steps to release -During this documentation, we assume the release is `$LAST_WALLABAG_RELEASE`. +During this documentation, we assume the release is `$LAST_WALLABAG_RELEASE` (like 2.3.4). -#### Files to edit +#### Prepare the release -- `app/config/config.yml` (`wallabag_core.version`) -- `CHANGELOG.md` (by using this command `github_changelog_generator --no-compare-link`. [github-changelog-generator is available here](https://github.com/skywinder/github-changelog-generator)) +- Update these files with new information + - `app/config/wallabag.yml` (`wallabag_core.version`) + - `CHANGELOG.md` +- Create a PR named "Prepare $LAST_WALLABAG_RELEASE release". +- Wait for test to be ok, merge it. -#### Create release on GitHub +#### Create a new release on GitHub - Run these commands to create the tag: - ``` - git checkout master - git pull origin master - git checkout -b release-$LAST_WALLABAG_RELEASE - SYMFONY_ENV=prod composer up --no-dev - git add --force composer.lock - git commit -m "Release wallabag $LAST_WALLABAG_RELEASE" - git push origin release-$LAST_WALLABAG_RELEASE - ``` - -- Create a new pull request with this title `DON'T MERGE Release wallabag $LAST_WALLABAG_RELEASE`. This pull request is used to launch builds on Travis-CI. -- Run these commands to create the package (you need to clone `https://github.com/wallabag/releaser`) : - - ``` - cd releaser/ - ./releaser.sh $LAST_WALLABAG_RELEASE - ``` - -- [Create the new release on GitHub](https://github.com/wallabag/wallabag/releases/new). You have to upload on this page the package. -- Delete the `release-$LAST_WALLABAG_RELEASE` branch and close the pull request (**DO NOT MERGE IT**). -- Update the URL shortener (used on `wllbg.org` to generate links like `http://wllbg.org/latest-v2-package` or `http://wllbg.org/latest-v2`) -- Update [the downloads page](https://github.com/wallabag/wallabag.org/blob/master/content/pages/download.md) on the website (MD5 sum, release date) -- Update Dockerfile https://github.com/wallabag/docker (and create a new tag) -- Update wallabag.org website (downloads, releases and new blog post) -- Drink a :beer:! +``` +git checkout master +git pull origin master +git checkout -b release-$LAST_WALLABAG_RELEASE +composer up +``` -### `composer.lock` -A release tag must contain a `composer.lock` file. It sets which dependencies were available at the time a release was done, -making it easier to fix issues after the release. It also speeds up `composer install` on stable versions a LOT, by skipping the -dependencies resolution part. +- Then continue with these commands: + +``` +git add composer.lock +git commit -m "Release wallabag $LAST_WALLABAG_RELEASE" +git push origin release-$LAST_WALLABAG_RELEASE +``` -Since `composer.lock` is ignored by default, either it must be removed from `.gitignore` _in the release branch_, -or it must be added using `git add --force composer.lock`. +- Create a new pull request with this title `Release wallabag $LAST_WALLABAG_RELEASE`. This pull request is used to launch builds on Travis-CI. +- Once PR is green, merge it and delete the branch. +- Run this command to create the package: + +``` +make release VERSION=$LAST_WALLABAG_RELEASE +``` + +- [Create the new release on GitHub](https://github.com/wallabag/wallabag/releases/new) by targetting the `master` branch or any appropriate branch (for instance backports). You have to upload the package (generated previously). +- Update the URL shortener (used on `wllbg.org` to update links like `https://wllbg.org/latest-v2-package` or `http://wllbg.org/latest-v2`) +- Update Dockerfile https://github.com/wallabag/docker (and create a new tag) +- Update wallabag.org website (downloads, MD5 sum, releases and new blog post) +- Put the next patch version suffixed with `-dev` in `app/config/wallabag.yml` (`wallabag_core.version`) +- Drink a :beer:! ### Target PHP version `composer.lock` is _always_ built for a particular version, by default the one it is generated (with `composer update`). -If the PHP version used to generate the .lock isn't a widely available one (like PHP 7), a more common one should +If the PHP version used to generate the .lock isn't a widely available one (like PHP 8), a more common one should be locally specified in `composer.lock`: ```json "config": { "platform": { - "php": "5.5.9", + "php": "7.1.3", "ext-something": "4.0" } }