[Vtigercrm-developers] SVN commit syntax

[Jeff Kowalczyk]

Allan Bush wrote:
> I'm glad to see more people taking advantage of the trac ticket
> system

I concur 100% in thanking the vtiger team for starting to use trac tickets
for their trunk development.

Here is the relevant documentation for the python script that handles this
integration of commit messages and the ticket system.

-----------

It searches commit messages for text in the form of:

  command #1
  command #1, #2
  command #1 & #2
  command #1 and #2
 
You can have more then one command in a message. The following commands
are supported. There is more then one spelling for each command, to make
this as user-friendly as possible. 

 closes, fixes
   The specified issue numbers are closed with the contents of
   this commit message being added to it.

 references, refs, addresses, re 
   The specified issue numbers are left in their current status, but
   the contents of this commit message are added to their notes. 


A fairly complicated example of what you can do is with a commit message
of:

   Changed blah and foo to do this or that. Fixes #10 and #12, and refs
   #12.

This will close #10 and #12, and add a note to #12.


-------------

Also be sure to aprise yourself of the trac syntax for embedding code and
revision references in your checkin messages. Makes browsing the
repository very easy. I used these in changesets such as:

http://vtiger.fosslabs.com/cgi-bin/trac.cgi/changeset/5114

  refs #62 and #17. merging source:vtigercrm/branches/4.2 r5080 through
  r5113 to source:vtigercrm/branches/4.2_postgresql_integration. allanbush
  fixed CreatePDF.php pdf generation bugs

That's a little overboard for routine commits, of course, but explicit
references to logical source and destination are very useful for merges
and other branching actions.

Thanks again to everybody creating all those tickets recently. If we can
get somebody with access to the database backend to update their
milestones (currently set to none), that would be a tremendous release
planning asset.