Release v3.0.9

[Trenloe]

I simply run through (ie study) the Patch List document (in detail) - I know my own code well enough that I can tell from that if anything's been changed

In my extensions I include an original, unmodified copy of each script/xml file I modify. When new rulesets come out I do a file compare between the new file and the original, unmodified file from the extension - if there are differences between the two files it will let you know if you need to update your extension. This is the only way to be 100% sure if there has/hasn't been any changes to the code that the extension uses in a new ruleset release.

[dulux-oz]

In my extensions I include an original, unmodified copy of each script/xml file I modify. When new rulesets come out I do a file compare between the new file and the original, unmodified file from the extension - if there are differences between the two files it will let you know if you need to update your extension. This is the only way to be 100% sure if there has/hasn't been any changes to the code that the extension uses in a new ruleset release.

Yeah, I do that too, but that's "Phase 2" which is only done if "Phase 1" says I should or if someone complains (and to date any complaints have turned out to be attributable to other people's code, not mine ).

Good tip, Tren

Cheers

[Ikael]

Yeah, I do that too, but that's "Phase 2" which is only done if "Phase 1" says I should or if someone complains (and to date any complaints have turned out to be attributable to other people's code, not mine ).

Good tip, Tren

Cheers

I have experienced that not all changes are recorded into changelog only those that really fix/change something, however those "undocumented" might cause issues in derived rulesets or in extensions. Personally I am storing all different versions of CoreRPG as is in my dev machine and when new version pops up I make diff by comparing all files to learn what has really changed. This also keeps me updated to how CoreRPG is developed and what is recommend way. Diffing is easy if you use right tools. I recommend it to be one step ahead of an error

[Nickademus]

What tools do you recommend Ikael?

[dulux-oz]

What tools do you recommend Ikael?

Winmerge is a good one for this - funnily enough, that's my "Phase 3"

Cheers

[Ikael]

I use kdiff3 to do all file scan/diff. You can also use this tool to do 3-way diff if needed. In addition to that I use wingrep to find what I want

[Nickademus]

Thank you both kindly.

[Moon Wizard]

I use CSDiff on my machine. I often need to compare changes between versions as well, in order to track down certain issues. Also, it's good for generating release notes.

Regards,
JPG