I certainly want to formalize a change log process, but there's not one in place. Honestly, I should add comments in SVN, but I've just been lazy. In particular, I want to track changes based on code given by the community. Right now I dont have any thankyous, which just feels wrong to me.
I've been considering taking up Simeon on his offer to host the project and put up a "Track" which provides SVN access, a wiki, a road map for the project and more. (Not to mention an actual project page.) Anyhow, I think once I hit beta I'll start keeping track of that stuff. Here's my general advice on moving from older versions to newer versions: 1) Delete the generated files. 2) Copy all your custom code out into a safe location. 3) Updated your config file 4) Regenerate all files 5) Copy your custom code into the correct locations. 6) Fix the Iterator-related issues 7) Test and fix other minor bugs. Doug -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of João Fernandes Sent: Thursday, February 23, 2006 5:25 PM To: [email protected] Subject: RE: [Reactor For CF] changelog? versioning? Well, I was about to reply that I didn't know how to check the current version of SNV but with tortoise you have an additional tab in folder properties that gives you that info. I don't know what kind of SNV software you're using but it should be some way to track it. Since we had so many changes since the beginning, I usually export reactor to a <head-revision> folder so I can then track if any previous code is broken. Anyway, a change log would be great, but I understand that Doug maybe doesn't have that much time. João Fernandes -----Original Message----- From: [EMAIL PROTECTED] on behalf of Mark Mazelin Sent: Thu 23-Feb-06 10:12 PM To: [email protected] Subject: [Reactor For CF] changelog? versioning? Doug: You have done a tremendous amount of work on Reactor and have put together a great and useful tool--thank you! In order to get a project I was working on completed, I was "forced" to check the Reactor code-base out of SVN at a certain point and commit to using it as it was without continuously updating it. Since then, judging by this mailing list, you have made many changes to the code, some of which are significant and API-related. Now I realize this is officially alpha code, so I'm not complaining. Rather, I am wondering if you keep any type of changelog or versioning records that will allow me to see which version of code I'm running, which version is current, and some type of outline of what changes I will need to make when I get to the point of wanting to upgrade the core Reactor code. If you don't have anything like this, does anyone have any good suggestions on how to do this? I can obviously comb through the mail archives, try to create a list of changes, perform those changes, then do trial-and-error to see what I missed, but that would be tedious, error-prone, and may produce bizarre errors that aren't easily tracked down. Mark -- Reactor for ColdFusion Mailing List -- [email protected] -- Archives at http://www.mail-archive.com/reactor%40doughughes.net/ -- Reactor for ColdFusion Mailing List -- [email protected] -- Archives at http://www.mail-archive.com/reactor%40doughughes.net/ -- Reactor for ColdFusion Mailing List -- [email protected] -- Archives at http://www.mail-archive.com/reactor%40doughughes.net/
