doc: Update release_process to clarify about GitHub tagging

[galak]

Add a note in the tagging section of the release process that explains
why using GitHub release process for tags should NOT be done.

Fixes #14985

Signed-off-by: Kumar Gala [email protected]

[codecov-io]

Codecov Report

❗ No coverage uploaded for pull request base (master@3c45eb4). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master   #14990   +/-   ##
=========================================
  Coverage          ?   52.93%           
=========================================
  Files             ?      309           
  Lines             ?    45266           
  Branches          ?    10451           
=========================================
  Hits              ?    23960           
  Misses            ?    16541           
  Partials          ?     4765

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 3c45eb4...b4a7a01. Read the comment docs.

[marc-hb]

Are you sure this issue affects pre-releases only? This page seems to tell github creates light-weight tags always: https://help.github.com/en/articles/working-with-tags

[marc-hb]

I looked at all tags with git for-each-ref refs/tags. I don't know how they were created but they're all annotated tags except these five light-weight tags:

v1.14.0-rc2
v1.9.1
v1.9.2
zephyr-v1.9.1
zephyr-v1.9.2

[galak]

Are you sure this issue affects pre-releases only? This page seems to tell github creates light-weight tags always: help.github.com/en/articles/working-with-tags

Looks like all github tags, will update the note.

[marc-hb]

Very surprising and confusing hence definitely worth mentioning.