Update release policy page

[veod32]

No description provided.

[Totktonada]

Commented below. Everything else does not contradict with my understanding of the processes.

[Totktonada]

In all supported releases, we also release a PATCH release as soon as we find and fix an outstanding CVE/vulnerability.

@kyukhin Please, decide whether this outstanding situation should be handled this way (via publishing a new release out of usual timelines).

Since our repositories have per-push packages, it is not necessary, maybe. However we should notify users about necessity to update and properly describe reasons.

[kyukhin]

In all supported releases, we also release a PATCH release as soon as we find and fix an outstanding CVE/vulnerability.

@kyukhin Please, decide whether this outstanding situation should be handled this way (via publishing a new release out of usual timelines).

Since our repositories have per-push packages, it is not necessary, maybe. However we should notify users about necessity to update and properly describe reasons.

Maybe just notify users about the patch. I see no reason for tagging new release in the case.

[Totktonada]

@veod32 Please, adjust the cited sentence accordingly.

[veod32]

@Totktonada All review comments have been resolved. Please review once again.

[Totktonada]

Thanks for the changes!

I looked over the resulting document and highlighted everything that contradits with my understanding or may be formulated better.

[veod32]

@Totktonada I've resolved all the comments. Also I restructured the content and re-wrote some of the paragraphs as we discussed. Some of the paragraphs are deleted as the contained the duplication of info.
Please review once again.

[Totktonada]

LGTM.

I gave several minor comments, but they are tiny and there is no need to re-review it with me.

Maybe @kyukhin want to take a glance at the final variant.