Please use numbers only for version NUMBER of nRF Connect SDK

Hello Nordic,

Please don't change the format of nRF Connect SDK version number from v2.2.0 to v2.2.99-dev3.    v2.2.99 is fine but no v2.2.99-dev3.  The dev2, dev3, dev 4 are not number and  it breaks the format and built tools and build scripts which expecting and parsing numbers.   If you need a new version number, just pump it up to v2.3.0 or v2.3.1.   Thanks.

JC

  • Hello JC, 

    Thanks for pointing this out. Please see Revisions in the nRF Connect SDK documentation. You must expect these versions from time to time, however, the official tags will not include these suffix.  The following lists all tags in our nRF Connect SDK.

    $ git tag
    v0.1.0
    v0.1.0-rc1
    v0.3.0
    v0.3.0-rc1
    v0.3.0-rc2
    v0.4.0
    v0.4.0-rc1
    v0.4.0-rc2
    v1.0.0
    v1.0.0-rc1
    v1.0.0-rc2
    v1.0.0-rc3
    v1.0.0-rc4
    v1.1.0
    v1.1.0-rc1
    v1.1.0-rc2
    v1.1.0-rc3
    v1.2.0
    v1.2.0-rc1
    v1.2.0-rc2
    v1.2.1
    v1.2.99-dev1
    v1.3.0
    v1.3.0-rc1
    v1.3.0-rc2
    v1.3.0-rc3
    v1.3.1
    v1.3.2
    v1.3.2-rc1
    v1.4.0
    v1.4.0-rc1
    v1.4.0-rc2
    v1.4.1
    v1.4.1-rc1
    v1.4.2
    v1.4.99-dev1
    v1.5.0
    v1.5.0-rc1
    v1.5.1
    v1.5.1-rc1
    v1.5.2
    v1.6.0
    v1.6.0-rc1
    v1.6.0-rc2
    v1.6.0-rc3
    v1.6.1
    v1.7.0
    v1.7.0-rc1
    v1.7.0-rc2
    v1.7.1
    v1.8.0
    v1.8.0-rc1
    v1.8.0-rc2
    v1.9.0
    v1.9.0-rc1
    v1.9.0-rc2
    v1.9.1
    v1.9.2
    v1.9.99-dev1
    v2.0.0
    v2.0.0-rc1
    v2.0.0-rc2
    v2.0.1
    v2.0.2
    v2.1.0
    v2.1.0-rc1
    v2.1.0-rc2
    v2.1.1
    v2.1.2
    v2.1.3
    v2.1.99-dev1
    v2.1.99-dev2
    v2.2.0
    v2.2.0-rc1
    v2.2.0-rc2
    v2.2.99-dev1
    v2.2.99-dev2
    v2.2.99-dev3
    

    Kind regards,
    Øyvind

Related