George,
Maybe the way RDJ does the roll back needs be addressed? I know versionRDJ has always reported the version line of the updated ruleset. Ruleset authors can use this feature to get a one-line change description to RDJ users when they are emailed. Based on my RDJ run logs, it seems that this used to happen more than it does now, but of course that's up to the Ruleset authors...
2 is nearing release, and this wouldn't be difficult to add: It could
check the cf file for a grep-able, commented, "this release" changes
entry, which may include a rules.htm#ChangesVerX url.
I suppose I could broaden the scope of the text returned for version reporting to allow for multiple lines, or explicitly code for changelog support.
Then if some change broke your site, you get a likely indicator why,When I get time I will revisit --lint. I also want to process linting each new file one at a time to try to isolate the broken files.
right there beside the roll back commands, near the lint output. And if
your update is multiple revisions behind, you have a url to get started
on finding changes at the relevant revision.
I don't understand... I assume you would prefer the notification to not knowing it was updated at all...?Actually, I like this proposed way of reporting changes a lot. I've always wondered the point of email notifications, "ruleset x has changed.." They kinda suggest I should do a diff and figure out if everything is really okay. I'd just assume see a change log as part of the notification that new rules have been loaded (or that lint prevented those changes from happening).
signature.asc
Description: OpenPGP digital signature
