Subject:*
Name/Email:*
Message Icon:*
Message:*
url email imgsrc image php hide code quote
English Nederlands 
SAMPLE
alignleft aligncenter alignright bold italic underline linethrough   


 [more...]
Options:*
 

 

 
     
Re: Using the trackers to document changes in the SVN

by marcan on 2007/12/19 19:54:29

Quote:

I have another request for the trackers - since we have several branches under active development, please indicate which branch produced the bug.


Absolutely.

Quote:

Should we create a group for each branch?


Yes. If anyone sees a group (branch, releases) or category that is not present in the tracker, please post here and someone with access will create them.
Re: Using the trackers to document changes in the SVN

by saganxis on 2007/12/19 17:51:24

Great important idea for developing!
Re: Using the trackers to document changes in the SVN

by davidl2 on 2007/12/19 15:22:44

Good idea
Re: Using the trackers to document changes in the SVN

by skenow on 2007/12/19 13:28:14

I have another request for the trackers - since we have several branches under active development, please indicate which branch produced the bug.

I think it was Dave that mentioned in another forum the first thing he does with a bug is try to reproduce it so he can validate it.

Our SVN repository is growing rapidly with new branches and tasks, so keeping ourselves very organized and maintaining the documentation is vital to our progress.

Should we create a group for each branch?
Re: Using the trackers to document changes in the SVN

by marcan on 2007/12/10 6:40:44

Ok good, we have started to use it. I saw others here have started to use it and I'm very glad !

Please document as much as possible everything you do with the tracker.

I also have another request. When one fixed a bug documented in the bug tracker, when you close the bug item, please post a message to document what you did, something like :
Quote:

Fixed and committed, revision XX


Where XX us the revision number associated with your changes.

And of course, in your commit message, you would have written something like :
Quote:

Fixing bug #12346 by implementing blablabla


That way, the bug and the fix are linked in 2 ways.

Any objection ?

Thanks !