diff --git a/development.md b/development.md
index 6971f586..dbdda2b9 100644
--- a/development.md
+++ b/development.md
@@ -35,18 +35,7 @@ After confirming that your changes pass local testing:
    all example images. This ensures that all example images are using the most up-to-date version of the SDK, i.e. the one including your
    changes.
 
-### After release
-
-Once a new version has been released, and its corresponding version tag exists on the remote repo, you want to update the `go.mod` 
-files to reflect this new version:
-```shell
-./hack/update_examples.sh -u <version>
-  ```
-After running the above, create a PR for the changes that the script made. Once merged, it will trigger the Docker Publish workflow.
-As a result, the correct SDK version will always be printed in the server information logs, 
-and the example images will always be using the latest changes (due to the local references).
-
 ### Adding a New Example
 
 If you add a new example, in order for it to be used by the Docker Publish workflow, add its path
-to the `dockerfile_paths` matrix in `build-push.yaml`.
\ No newline at end of file
+to the `dockerfile_paths` matrix in `.github/workflows/build-push.yaml`.
\ No newline at end of file
diff --git a/releases.md b/releases.md
new file mode 100644
index 00000000..50642e26
--- /dev/null
+++ b/releases.md
@@ -0,0 +1,24 @@
+# Release Guide
+
+This document explains the release process for the Go SDK. You can find the most recent version under [Github Releases](https://github.com/numaproj/numaflow-go/releases).
+
+### How to Release
+
+This can be done via the Github UI. In the `Releases` section of the Go SDK repo, click `Draft a new release`. Create an appropriate tag for the new version and select it. Make 
+the title the same as the tag. Click `Generate release notes` so that all the changes made since the last release are documented. If there are any major features or breaking
+changes that you would like to highlight as part of the release, add those to the description as well. Then set the release as either pre-release or latest, depending
+on your situation. Finally, click `Publish release`, and your version tag will be the newest release on the repository.
+
+### After Release
+
+Once a new version has been released, and its corresponding version tag exists on the remote repo, you want to update the `go.mod`
+files to reflect this new version:
+```shell
+./hack/update_examples.sh -u <version>
+  ```
+After running the above, create a PR for the changes that the script made. Once merged, it will trigger the Docker Publish workflow.
+As a result, the correct SDK version will always be printed in the server information logs,
+and the example images will always be using the latest changes (due to the local references).
+
+If the released version has backwards incompatible changes, i.e. it does not support older versions of the Numaflow platform,
+you must update the `MinimumNumaflowVersion` constant in the `pkg/info/types.go` file to the minimum Numaflow version that is supported by your new SDK version. 
\ No newline at end of file