Release procedure question

In releases.txt:

   1. Tweak trunk/CHANGES to contain all the latest changes. Commit.
   2. Bump the version numbers in svn_version.h and CHANGES. Commit.
   3. Create the release branch for building the release

Is there a reason why one would commit the CHANGES and svn_version.h
changes _before_ creating the release branch? This seems
counter-intuitive. I would expect to create the branch, then make
changes, then merge them back to /trunk at some point.

Or, does it not matter, since it's effectively the same thing ?

Thanks,

-- 
Seeya,
Paul
--
Key fingerprint = 1660 FECC 5D21 D286 F853  E808 BB07 9239 53F1 28EE
	It may look like I'm just sitting here doing nothing,
   but I'm really actively waiting for all my problems to go away.
	 If you're not having fun, you're not doing it right!
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org