• Hi gqevu6bsiz,

    would it be possible to stick with 3, maximum of 4 numbers in the version number/tag please?

    The current version 1.5.2.8.1 is too long for Composer to be able to install it, WPackagist doesn’t recognise it as well.

    I reckon it would be best to go with 1.5.3, 1.5.4 as http://semver.org/ recommends, or, if you really need, 1.5.2.9, 1.5.2.10 for the really minor-minor changes. It’s unusual but the tools can still handle it.

    Five versioning levels are basically too much. Do you have a system in your versioning scheme? Or you just add numbers when something changes?

    Let me know if you need to discuss further.

    Cheers
    Michal

    https://ww.wp.xz.cn/plugins/wp-admin-ui-customize/

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author gqevu6bsiz

    (@gqevu6bsiz)

    Hi michalkleiner,

    Thank you for your feedback.

    http://semver.org/

    And many thank for it information. I did not know until now.
    I was able to some of understand.

    I was able to understand your meaning. I was the version management method for me until now.
    Roughly in other words: Big specification changes . Medium specification changes . Major bug fixes . Minor bug fixes . Very minor bug fix

    I will versioning to X.Y.Z in future.(maximum 3 and it is aware of the backward compatibility)
    I will release as 1.5.3 in the near future after fix a little specification Change.

    I’m sorry if my understand is wrong, please point out.

    Thanks,
    gqevu6bsiz

    Thread Starter michalkleiner

    (@michalkleiner)

    Great, thanks gqevu6bsiz!

    I think you understood it well and hopefully the link on how to release versions was useful for you too.

    Cheers,
    Michal

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

The topic ‘Versions numbering’ is closed to new replies.