Hi, > How can this or other commits on master branch prevent creating new > tag REL_18_BETA2 or forking REL_18_STABLE from master? Perhaps, this > commit is not the only one on master branch after tag REL_18_BETA1.
Right, but I see people fixing whitespaces and documentation for PG18 in the `master` branch right now. My humble understanding is that `master` is basically REL_18_STABLE at the moment. If one wants to fork REL_18_STABLE for instance, either the branch will include your change (which we probably don't want), or one will have to manually revert it, or create a fork from BETA1 and cherry-pick all the necessary changes from `master`. This is the reason why I suspected this was committed by mistake. -- Best regards, Aleksander Alekseev
