Changelog Request / Suggestion
Suggestions
brian:
Can you let me know what issues you think you might run into? Maybe that will clarify it for me so I better understand what you're hoping to avoid happening.
Let's say I've got a custom template which I made based on the variables of the Elastic Template. I'm just stating this as an example - if you decided to change
to
or spotted a place where you misused != and not it need to be ! instead.
or if you added a completely new variable to the template:
Just put a "yes" or "no" in the changelog letting me know that something other than HTML or CSS has changed.
I'm only using the above as examples. But assuming that most people will create a template based off of the existing templates, they'll be a lot of code coming from the JR templates and used in the custom templates.
Obviously, if only the module PHP code changed in the PHP files, or there was a HTML or CSS change then the Variable notice would be "No" meaning I wouldn't have to look over my templates for a code based change.
Not asking you to list the changed variable, just a notice that a variable has changed and custom skinners would need to look over the code in the template files.
brian:
Sure - if we have a security update I can mark it "high priority" or something - most likely you'll see a forum post about it too.
That would be great. Someone who has a highly custom site that isn't going to just click the update button might need to determine which update needs to take priority. I would actually love to see in every changelog Security Level: Low, Moderate, High at the top of each update. I'm sure you would agree, security is one of the most important things to know about. Putting it in every update as the default first line would also tell other developers of modules - put security on the first line versus include it if there is a security issue.
updated by @jimmy: 02/13/15 11:19:49AM