Bugs & comments

[Nutter]

I'm working on an web app that is intended to be open source, and am looking for suggestions on keeping track of where bugs were fixed. My thought is to add a comment with // See bug #123 above the fix and maybe // end bug #123 below it. Does this sound like a good solution? Do any of y'all do something similar? Any better suggestions?

[coopster]

Have you considered versioning software like CVS or SubVersion [subversion.tigris.org]?

[Nutter]

Nope, sure haven't :-)

Can you explain how that works? I've got a folder on my fileserver that is mapped to both a share through Samba and a web folder through Apache. So I edit the files live, hit refresh to check, and when they work move on. Where does a versioning program come in?

[Nutter]

Double check me to see if I have the idea down...

1 - Install a version program
2 - Create a repository
3 - Move my current source to that repository
4 - Check out from that repository back to my folder where I've been editing. Or, somewhere new.
5 - Keep editing as before
6 - When I've got a version ready to put together commit the changes

[coopster]

Yep, sure sounds easy, doesn't it ;)

[Nutter]

Looks like I've got something to read today. I just download the 350+ page pdf manual to my palm.

Thanks for the suggestion. It looks like it'll help out a lot. I had actually used a CVS without knowing it was called that back when I was writing database apps in VB6.