Updated CHANGELOG.md for 0.2.0 release. (#422)

* Updated CHANGELOG.md for 0.2.0 release.

* Change date format in CHANGELOG.md & updated CONTRIBUTING.md

* Updated CONTRIBUTING.md

* Update CONTRIBUTING.md

CHANGELOG.md

@@ -4,7 +4,9 @@ All notable changes to this project will be documented in this file.
 
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/), with an added `List of PRs` section and links to the relevant PRs on the individal updates. This project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
-## [Unreleased](https://github.com/askap-vast/vast-pipeline/compare/0.1.0...HEAD)
+## [Unreleased](https://github.com/askap-vast/vast-pipeline/compare/0.2.0...HEAD)
+
+## [0.2.0](https://github.com/askap-vast/vast-pipeline/releases/0.2.0) (2020-11-30)
 
 #### Added
 
@@ -164,7 +166,7 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 - [#305](https://github.com/askap-vast/vast-pipeline/pull/305) feat: 2 epoch metrics
 - [#345](https://github.com/askap-vast/vast-pipeline/pull/345) feat, fix: Website improvements.
 
-## [0.1.0](https://github.com/askap-vast/vast-pipeline/releases/0.1.0) (2020/09/27)
+## [0.1.0](https://github.com/askap-vast/vast-pipeline/releases/0.1.0) (2020-09-27)
 
 First release of the Vast Pipeline. This was able to process 707 images (EPOCH01 to EPOCH11x) on a machine with 64 GB of RAM.
 

CONTRIBUTING.md

@@ -45,11 +45,11 @@ In to order to make a release, please follow these steps (example: making the `0
 
 1. Make sure that every new feature and PR will be merged to master, before continuing with the releasing process.
 2. Update the [`CHANGELOG.md`](./CHANGELOG.md) on `master` directly (only admin can and need to force-push the changes) with the list of changes. An example of format can be found [here](https://github.com/apache/incubator-superset/blob/master/CHANGELOG.md).
-3. The `0.1.X` branch will be updated by merging `master` into `0.1.X`.
-4. Branch off `0.1.X` and call it `0.1.1`, then change the `package.json` with the version of the release, commit and tag the commit. Push commit and tag to origin.
+3. The `0.2.X` branch will be updated by merging `master` into `0.2.X`.
+4. Branch off `0.2.X` and call it `0.2.1`, then change the `package.json` with the version of the release, commit and tag the commit. Push commit and tag to origin.
 5. Make a release in GitHub using that tag.
 
-__NOTE__: keep the version on `master` branch to something like 99.99.99dev and in `0.1.X` branch to something like 0.1.99dev. In the release branch, change only the version in [`package.json`](./package.json).
+__NOTE__: keep the version on `master` branch to something like 99.99.99dev and in `0.2.X` branch to something like 0.2.99dev. In the release branch, change only the version in [`package.json`](./package.json).
 
 ## Solving your `models.py`/migrations issues