Update versioning.rst (#205)

* Update versioning.rst

Added a note atop the file to clarify versioning, and I tried to write it in a timeless way so that it won't have to be updated again. That said, please fact check the note and its links, and feel free to edit the note directly if need be. Thanks.

* Update versioning.rst

Fixed a bracket on a link.

* Update versioning.rst

Changed link format on the new versioning note atop the file from markdown to rst.

* Update docs/developer_guide/contributor_guide/versioning.rst

Co-authored-by: Hardik Windlass <108932456+hwindlas@users.noreply.github.com>

---------

Co-authored-by: achamuah <106507758+achamuah@users.noreply.github.com>
Co-authored-by: Hardik Windlass <108932456+hwindlas@users.noreply.github.com>
Co-authored-by: Sonia Bhattacharya <sonia.bhattacharya@intel.com>

Author: 4 people

docs/developer_guide/contributor_guide/versioning.rst

@@ -1,6 +1,9 @@
 Versioning
 ==========
 
+Note: The Edge Manageability Framework repository and its documentation repository follow the calendar-based versioning format of the Open Edge Platform: `YEAR-BASED MAJOR.MONTH.PATCH`. Their respective release numbers are published in the `VERSION <https://github.com/open-edge-platform/edge-manageability-framework/blob/main/VERSION>`__ file of the framework repository and the `VERSION <https://github.com/open-edge-platform/edge-manage-docs/blob/main/VERSION>`__ file of the documentation repository.
+All other component repositories within the Edge Manageability Framework continue to use their own versioning schemes and branching strategies as described below.
+
 Versioning is an integral part of the code review and Continuous Integration
 (CI) process, and releasing a new version of a component will be an extremely
 lightweight and frequent event.