Merge pull request #942 from thewilli/fix-wiki-links

[github/shaarli/Shaarli.git] / doc / md / Release-Shaarli.md

diff --git a/doc/md/Release-Shaarli.md b/doc/md/Release-Shaarli.md
index 0e445272e182799b8fa068d04ab01a2486b2305e..974a743861994dc44126f69329a90537898f89ad 100644 (file)
--- a/doc/md/Release-Shaarli.md
+++ b/doc/md/Release-Shaarli.md
@@ -3,6 +3,7 @@ releases](http://git-scm.com/book/en/v2/Distributed-Git-Maintaining-a-Project#Ta
 
 ## Prerequisites
 This guide assumes that you have:
+
 - a GPG key matching your GitHub authentication credentials
     - i.e., the email address identified by the GPG key is the same as the one in your `~/.gitconfig` 
 - a GitHub fork of Shaarli
@@ -25,6 +26,7 @@ GitHub allows drafting the release note for the upcoming release, from the [Rele
 This file should contain the same information as the release note draft for the upcoming version.
 
 Update it to:
+
 - add new entries (additions, fixes, etc.)
 - mark the current version as released by setting its date and link
 - add a new section for the future unreleased version
@@ -43,32 +45,13 @@ TBA
 ```
 
 
-## Increment the version code, updated docs, create and push a signed tag
-### Generate documentation
-```bash
-$ cd /path/to/shaarli
-
-# create a new branch
-$ git fetch upstream
-$ git checkout upstream/master -b v0.5.0
-
-# rebuild the HTML documentation from Markdown
-$ make htmlpages
-
-# commit the changes
-$ git add doc
-$ git commit -s -m "Generate documentation for v0.5.0"
-
-# push the commit on your GitHub fork
-$ git push origin v0.5.0
-```
-
+## Increment the version code, update docs, create and push a signed tag
 ### Create and merge a Pull Request
 This one is pretty straightforward ;-)
 
 ### Bump Shaarli version to v0.x branch
 
-```
+```bash
 $ git checkout master
 $ git fetch upstream
 $ git pull upstream master
@@ -125,6 +108,7 @@ Update `README.md` so version badges display and point to the newly released Sha
 
 ### Create a GitHub release from a Git tag
 From the previously drafted release:
+
 - edit the release notes (if needed)
 - specify the appropriate Git tag
 - publish the release
@@ -132,6 +116,7 @@ From the previously drafted release:
 
 ### Generate and upload all-in-one release archives
 Users with a shared hosting may have:
+
 - no SSH access
 - no possibility to install PHP packages or server extensions
 - no possibility to run scripts
@@ -146,6 +131,7 @@ $ make release_archive
 ```
 
 This will create the following archives:
+
 - `shaarli-vX.Y.Z-full.tar`
 - `shaarli-vX.Y.Z-full.zip`