You are reading a single comment by @DrAzzy and its replies. Click here to read the full conversation.
  • I would like to humbly suggest a simple change to the version numbering used on Espruino.

    Right now, unless you start digging, something compiled from github is hard to tell apart from the next released version. Have you thought about doing something like what apache does. They use even numbers for "stable" releases, and odd numbers for development ones.

    IE, the process I would propose is:
    *Release version 80 (even number, release)
    *Immediately bump version to 81
    *Commit changes normally
    *bump version to 82, then immediately release
    *bump version to 83 immediately (and so on)

    That way, if we see an odd numbered build, we know it's "between" two released versions - so when someone says "This works with v82 and later", we won't need to know if we used a github build for v82, because all the github builds will be either v81 or v83.

    Of course, there are many ways to achieve the same effect - I just don't think the current situation, where "you need v82" really means "you need the release v82, not a github v82 which looks the same".

    Do other people like this idea?

About

Avatar for DrAzzy @DrAzzy started