admin v2.1 release process

some fixes on the repository

Create the 2.0 tag

• The current version 2.0 does not have a tag

git checkout master
git tag -a -m "Create the pgRoutingLayer-2.0.0 tag" pgRoutingLayer-2.0.0
git push --tags

• make the release: https://github.com/pgRouting/pgRoutingLayer/releases/tag/pgRoutingLayer-2.0.0

Create branch develop

• There is no branch develop, so the developed code for 2.1.0 would have merged to develop, so develop will contain that development

git checkout vdev/pgr-2.1.0
git checkout -b develop
git push --set-upstream origin develop

Tasks before merging

• Review issues and close the ones solved with this release
• Link of closed issues with the release: https://github.com/pgRouting/pgRoutingLayer/issues?q=is%3Aissue+milestone%3A%22Release+2.1.0%22+is%3Aclosed

Update master with latest develop

• make pull request from github site

  • make sure its to master on pgRouting/pgRoutingLayer because it automatically points to Anita's repository

• follow the instructions (because of conflicts)

git checkout develop
git merge master
git status

• Fix the conflicts From the last line the merging conflicts will show.

• follow the instructions (because of conflicts)

git commit -a -m 'fixed merge conflicts'
git checkout master
git merge --no-ff develop
git push origin master

Create the 2.1.0 tag

• The current version 2.1 make the tag

git checkout master
git tag -a -m "Create the pgRoutingLayer-2.1.0 tag" pgRoutingLayer-2.1.0
git push --tags

• make the release: https://github.com/pgRouting/pgRoutingLayer/releases/tag/pgRoutingLayer-2.1.0
• Put the link of the closed issues
• Add some comments about changes

upload the zipped plugin code

A plugin is published when you upload the zipped plugin code to plugins.QGIS.org. This is usually done manually.

• Upload plugin