WTF is up with not providing a changelog?

Viewing 4 replies - 1 through 4 (of 4 total)

  • Hi,

    We’re releasing a new major version of our plugin soon and were testing a new deployment process in with a copy of the current version of the plugin. The changelog wasn’t updated because no changes were made. Version 3 of our plugin will include a changelog.

    Thanks,
    John

    • This reply was modified 8 years, 6 months ago by jwineman.
    Thread Starter pjv

    (@pjv)

    Thanks, allow me to beg then that the proper changelog for v. 1.3.25 is something like:
    ‘Testing new deployment process – no changes to plugin’.

    That way, those of us who prefer not to experience WSOD’s from errant upgrades will know that it is probably safe to go ahead and update without having to diff the new version against the old one.

    Yup, completely agree!

    New change log will follow this format:
    https://github.com/cloudflare/CloudFlare-CPanel/blob/master/CHANGELOG.md

    As a suggestion, between tests, could you restore the Stable Tag to 1.3.24 so my WordPress management system stops notifying me of the CF plugin update.

    I’m a plugin developer myself. Not a fan of SVN, either. I find SmartGit to be a nice way to manage SVN and Git repositories.

    Look forward to seeing version 2 (and 3) of the CloudFlare plugin.

    Thanks guys!

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘WTF is up with not providing a changelog?’ is closed to new replies.