Change log?
by dylanrw · in Torque Game Engine Advanced · 11/12/2006 (6:15 pm) · 10 replies
Am I missing something? Is there a change log so we can see whats changed from 4.0 to 4.1 as supposed to doing a diff?
About the author
#3
11/14/2006 (6:12 am)
Isnt it more fun to discover them on your own? =) 
#4
11/14/2006 (12:15 pm)
I can't recall there ever being a changelog for TSE
#5
lol hardly, I'm not used to having to go through all the source checking diffs, usually there is some sort of changelog with almost all of the software I've ever had to work with/compile... and it also burns way too much time... oh well.
11/14/2006 (2:16 pm)
"Isnt it more fun to discover them on your own? =)"lol hardly, I'm not used to having to go through all the source checking diffs, usually there is some sort of changelog with almost all of the software I've ever had to work with/compile... and it also burns way too much time... oh well.
#6
11/14/2006 (5:30 pm)
Yeh, with the removal of the CVS server, its even harder to look at the files that have changed without doing a full diff... and you are right, it does burn alot of time, but apparantly our time is cheaper than GG's.. As that was one reason I saw that the CVS repo was pulled, because its cost outweighed the benefits...
#8
Safe to assume that goes for the distribution methods as well.
Patience is a virtue. :)
11/16/2006 (10:34 pm)
Let's not forget that this is not a "live" product and is still in development.Safe to assume that goes for the distribution methods as well.
Patience is a virtue. :)
#9
With EA milestones this level of QA clearly isn't going to happen to the same degree, and stuff will and does break across release; quite frequently I might add. As EA developers, this goes with the territory of course, but knowing *what* changed helps one find out *where* things may have broken, usually in a fraction of the time vs. starting blind.
Even without the public CVS, I'm assuming internally *some* form of source control must be used for a project the size of TSE!?! If so, the sum of the changelogs could be generated and included in the deployment bundle as a simple change.txt or something. If Perforce was being used such a report would be trivial to generate.
I guess what I'm saying is that a changelog should be available for viewing, even if there is no public CVS server. It may be not as flexible as having access to the repository, but it'll be better than nothing.
- Ryan
11/27/2006 (6:15 am)
The fact that it is not a "live" product means the changelog is even more important; not less. With a "live" release, one can expect the code to have gone through several levels of QA to make sure there were minimal regressions. Bugs and regressions are still a fact of life, but far less common than while in EA state.With EA milestones this level of QA clearly isn't going to happen to the same degree, and stuff will and does break across release; quite frequently I might add. As EA developers, this goes with the territory of course, but knowing *what* changed helps one find out *where* things may have broken, usually in a fraction of the time vs. starting blind.
Even without the public CVS, I'm assuming internally *some* form of source control must be used for a project the size of TSE!?! If so, the sum of the changelogs could be generated and included in the deployment bundle as a simple change.txt or something. If Perforce was being used such a report would be trivial to generate.
I guess what I'm saying is that a changelog should be available for viewing, even if there is no public CVS server. It may be not as flexible as having access to the repository, but it'll be better than nothing.
- Ryan
#10
11/29/2006 (10:19 am)
Winmerge... thats LIKE a changelog :) 
Torque Owner Jeremiah Fulbright