Release process and tagging strategy

[Sebastien <se...@gmail.com>]

Hi Martijn,

I pulled the new tags 'wicket-7.2.0' and 'rel/wicket-7.2.0'

And I realized something strange:
- If I checkout wicket-7.x, I am *not* able the see the tag(s) in "git
changelog"...
- But if I checkout the tag (rel/wicket-7.2.0), I am able to see them.

adcd324 (HEAD, tag: wicket-7.2.0, tag: rel/wicket-7.2.0)
[maven-release-plugin] prepare release wicket-7.2.0

So it makes me realizing that you are preparing the release in a dedicated
branch, but you didn't merge created commits back to source branch (master,
wicket-7.x, etc). The problem is that the tags are created on those
commits, so we cannot see them in the source branch...

I wasn't there at the beginning of the release process, so I don't know if
it's intentional or not... And I am thinking that the release strategy is
probably the same for all Apache projects... But if you have some
enlightenment on the how/why... :)

Many thanks in advance,
Sebastien.