Using the trackers to document changes in the SVN

Hi guys,

In order to better document and follow up the changes we do in our SVN, what do you think about the following.

Before coding something new of fixing a bug, we add an item either in the bug tracker, or the feature tracker, or for larger things, in the task tracker.

Then we code it, commit it, and make sure to link our SVN commit message with the ID of the item we created.

That way, changes will truly be documented and opened for commenting by other developer which is a very good thing.

For example, yesterday, I added the multilanguage feature. I did not add an item in the tracker. So today I found out 2 things.

1- Rodriguo already did something similar in Xoopers.
2- I forgot to change the install process to add the new config options in the databse, same thing for the upgrade script.

If I had added a task or feature requesy at SF for this, may Rodriguo could have told me he already did it, and david and nekro could have documented that it was not working.

I'm going to add a task for the ML now

Thoughts ?

I agree with this - if I had posted that I was working on the system templates, it would have eliminated a conflict that arose when the latest 2.0.18rc changes were committed.

Let's give it a start

+1

gets my vote.

simplicity at it's best :)

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:
Where XX us the revision number associated with your changes.

And of course, in your commit message, you would have written something like :
Quote:
That way, the bug and the fix are linked in 2 ways.

Any objection ?

Thanks !

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?

Good idea

Great important idea for developing!

Quote:
Absolutely.

Quote:
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.