Incorrect plugin versioning

  • Resolved peterjgordon

    (@peterjgordon)


    6 years, 7 months ago

    Hi, I noticed this plugin has been incorrectly versioned as ‘2.40’ instead of ‘2.4.0’. This will cause issues with our automatic updating process and will be confusing for users in the future. What are your plans to avoid these issues? Going back to ‘2.5’ next would actually be an older version.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author WebFactory

    (@webfactory)

    6 years, 7 months ago

    Hi,

    I have to say I’m quite taken by this. Not saying we’re right here but been using the “one dot notation” for 10 years on like 50 plugins and had no problems so far.

    The next version for us would be 2.45. Are you sure that would be “older” than 2.45 and what code/system would claim that?

    Thread Starter peterjgordon

    (@peterjgordon)

    6 years, 7 months ago

    Hi,

    Thanks for your reply. My concern was that this was an accidental change so I wanted to check to ensure the next version wouldn’t be 2.5. Indeed, as you say, versioning with one dot notation is very common and there shouldn’t be a problem with it!

    Thanks,
    Peter

    Plugin Author WebFactory

    (@webfactory)

    6 years, 7 months ago

    Glad we got that sorted out. Was afraid we’ll need to change the versioning scheme on all our plugins 🙂

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

The topic ‘Incorrect plugin versioning’ is closed to new replies.