Do you manage your vB modifications and plugins in a VCS like CVS or Subversion?

[softjury]

Hi,

i'm interested in how you people manage your code related to vBulletin plugins, vBulletin releases, your own plugins and especially on updates of these.

At my company i've put the vbulletin source code including the plugins and all other vbulletin related code in a Subversion repository.

I keep branches of each official released version, making diffs between these versions and then can merge/apply these changes between version to my current version in TRUNK.

For doing this in an effective manner i have to strip all the vBulletin comments in the header and footer of each php, js, css file (the comments that contain the vbulletin version number, when i downloaded my copy from vbulletin member area, etc.) because when not doing so many files seem to have changed when in fact only the version number in the comment has.

How do you manage your vBulletin code?

[Sparky McSmith]

I keep branches of each official released version, making diffs between these versions and then can merge/apply these changes between version to my current version in TRUNK.

It sounds like I maintain my code very similarly to the way you maintain yours - I really can't think of a better way to do it, though I'm also curious what other folks do.

For doing this in an effective manner i have to strip all the vBulletin comments in the header and footer of each php, js, css file (the comments that contain the vbulletin version number, when i downloaded my copy from vbulletin member area, etc.) because when not doing so many files seem to have changed when in fact only the version number in the comment has.

How do you do this? Any particularly elegant solution? I'm just using UltraEdit to search/replace/remove.

[Sparky McSmith]

I'm still surprised at how few mod-developers actually use a version control system.

Would it be wonderful if all mods were maintained on github?