[proposal] Keep draftversion as 'true' in the 'main' branch

[amilendra]

Thank you for submitting a proposal!

We are looking forward to evaluate your proposal, and if possible to
make it part of the Arm C Language Extension (ACLE) specifications.

We would like to encourage you reading through the contribution
guidelines, in particular the section on submitting
a proposal.

From what I understand the draftversion of main should always be true.

However when a release branch is created based on main, draftversion is set to false in the branch, and when the release branch is merged back to main, draftversion also is unintentionally set to false.
Then it is the responsibility of the person creating the first change after the release to move draftversion back to true (because without that CI fails), even if the change has nothing to do with draftversion.

So could we improve the release process so that this is not required by people making unrelated changes?
I have the following possible solutions

1. The release process adds a step to set draftversion to true right after merging the release branch to main
2. Remove the need to merge a release branch to main. I think the need to merge the release branch to main is because during the release process some changes are done to the release branch which are then merged to main in one go. I am not that familiar with the process but it may be possible to first make those changes to main, and then cherry-pick them to the release branch.