Create RELEASE.md file for release notes.

People creating PRs will be responsible for updating the release notes themselves, for major features and bug fixes. Whatever is in the release notes at the time of a release will go out, with some possible editing.

PiperOrigin-RevId: 321267749

Author: alanchiao

CONTRIBUTING.md

@@ -32,6 +32,9 @@ See these [guidelines](CONTRIBUTING_TECHNIQUE.md).
 
 Please wait until we finish this section.
 
+New features and bug fixes for documented features should come with a
+modification to the [release notes](RELEASE.md).
+
 ## Code reviews
 
 All submissions, including submissions by project members, require review. We

RELEASE.md

@@ -0,0 +1,26 @@
+<!--
+See https://github.com/tensorflow/model-optimization/releases/ for previous
+examples of release notes. This project follows https://semver.org/.
+
+"Tested against" references the versions of TensorFlow that TFMOT unit tests
+will be run against prior to release. For 2.X, only the earliest (2.0.0) and latest (nightly)
+TF releases are tested against, under the assumption that everything in between
+works sufficiently well enough.
+-->
+
+# Release following 0.3.0
+
+Keras quantization API:
+
+ * Major Features and Improvements
+   *
+ * Bug Fixes and Other Changes
+   * Fixed Sequential model support for BatchNorm layers that follow Conv/DepthwiseConv ([issue](https://github.com/tensorflow/model-optimization/issues/378)).
+   * Improved error message for not using `quantize_scope` with custom Keras layers and objects.
+ * Tested against TensorFlow nightly
+
+Keras pruning API:
+
+ * Tested against TensorFlow 1.14.0, 2.0.0, and nightly.
+
+