chore: update development and releasing docs to reflect latest changes (#184)

Signed-off-by: a3hadi <[email protected]>

Author: ayildirim21

development.md

@@ -6,10 +6,11 @@ This document explains the development process for the Numaflow Python SDK.
 
 1. Install [Poetry](https://python-poetry.org/docs/) before starting your test. Make sure you have the correct Python version
 2. Make your SDK changes
-3. Update the `example.py` inside the same example directory if needed 
-4. Run `make image` inside the same example directory to build your image
-5. Now that you have the image with your customized example and code change, you can test it in a Numaflow pipeline. Example pipelines, `pipeline.yaml`, are also provided in most of the example directories.
-Please check [Numaflow](https://numaflow.numaproj.io/) for more details
+3. Update the `example.py` file inside the desired example directory if needed 
+4. Run `make image TAG=<tag>` inside the same example directory to build your image with an appropriate tag
+5. Now that you have the image with your customized example and code change, you can test it in a Numaflow pipeline. 
+Example pipelines, `pipeline.yaml`, are also provided in most of the example directories. Ensure to update the image tag in
+the `pipeline.yaml` file to the one you used when building your image
 
 Each example directory has a Makefile which can be used to build, tag, and push images.
 If you want to build and tag the image and then immediately push it to quay.io, use the `image-push` target.

releases.md

@@ -13,7 +13,7 @@ the version in the root `pyproject.toml` should be updated (for [reference](http
 you must update the `MINIMUM_NUMAFLOW_VERSION` constant in the `pynumaflow/info/types.py` file to the minimum Numaflow version that is supported by your new SDK version
 3. After making these changes, create a PR. Once merged, it will trigger the `Docker Publish` workflow, and should be included in the release.
 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 referencing the local SDK tarball that is built)
+the example images will always be using the latest changes (due to the local references)
 
 ### How to Release