Skip to Content
 

Change Tracking

1 reply [Last post]
FastLearner
Offline
Joined: 12/31/1969

I propose that we figure out a centralized place to keep track of code changes made to the site. I'm not particularly worried about things becoming broken (I always save previous versions of the page if I make any changes and worst-case we can reinstall the module in question) but I am slightly concerned about needing to track down all of the needed changes again after a board upgrade.

Obviously I made quite a few changes to the journals main page. I more-or-less documented them in the code, but I didn't exactly explain why I made the changes most of the time.

Any thoughts on a good centralized place to store them?

(PS to hpox: this was inspired by a little change I made so that ghost topics don't appear in the forums block -- whle it only took about 10 seconds to change it did take a few minutes to track down the change needed.)

hpox
Offline
Joined: 12/31/1969
Change Tracking

I know what you're talking about. Sometimes, tracking the exact location of the problem/change is a real pain.

Syndicate content


forum | by Dr. Radut