During software development (especially done in agile way) there are often time when working software release must be prepared for customer evaluation of internal testing. I found many software release managers use a feature called “commit freeze“: no one can commit to main branch of development (trunk/master) until release is packaged. I doubt if it is really required.
The possible reason for freezing commits:
Correcting comments of existing commits is easy if you have enough privileges on subversion repository:
svn propedit -r <revision-number-here> --revprop svn:log "<new log message>" <url>
That’s all. Pretty simple.
http://subversion.tigris.org/faq.html#change-log-msg
I’ve been using many version control systems in software development projects. I’m aware Subversion is not the best version control system out there, but it’s most popular (at least among enterprise projects I’ve been working on).
I’m describing here Subversion usage best practices that come from my experience with Subversion (or other version control systems) collected on many projects. Some suggestions are related strictly to Subversion, some are general.
During a merge from branch on the same repository as current copy:
svn merge -r17007:17249 http://hostname/svn/path
I got the error: svn: Malformed URL for repository. The fix is to add user name in SVN URL:
svn merge -r17007:17249 http://dcieslak@hostname/svn/path
Is this a Subversion bug? Probably the problem is that my username placed in SVN config file has form: domainname\username. Maybe SVN merge cannot handle that format?
