d.o instructions are for 7.x branch regardless of currently selected

Am I missing something? The branch or release must have been created in order for it to exist as a choice in the drop down, which renders the directions unnecessary.

Oh, I see, it's only the directions about tagging for a release that should have a dynamic branch? Can you provide a concrete example, including the 'note about this,' that would be adequately clear?

Still not clear what you're suggesting as there are directions for both dev and stable releases.

We'd communicate more clearly if you provided a concrete example rather than a description of the change you're proposing. For example, do you mean:

Tag for a stable release

git checkout [7.x-1.x] <--fill this with a currently selected branch? 
git tag [7.x-1.0] <-- Replace the .x  above with .0  (and will this always be correct? Is there never a 1.1?)
git push origin [7.x-1.0]

I completely missed the screencap, which does make this more clear.

Moving this to a feature request.

Replacing 7.x-1.x with the selected branch should work by using @branch placeholder.

Filling in 7.x-1.0 is more difficult as we would have to lookup the existing tags to find the last tag tied to the current branch and increments on that.

To replace 7.x-1.x with @branch we should that the branchname follows the naming convention, it should not be a feature branch...

Replacing 7.x-1.0 would require a function to generate a recommended next release version. Feel free to open an issue to hash that out.

I'm closing this issue for-now.