Chronologic Versioning: No more arbitrary version updates and regressions

Re:Chronologic Versioning: No more arbitrary version updates... by naniwaduni on Thursday January 02, 2020 @08:20AM (#21935100)

How are you going to relabel it when you can't yank it?

[ Parent | on HN ]

Re:Chronologic Versioning: No more arbitrary version updates... by kstenerud on Thursday January 02, 2020 @08:44AM (#21935257)

You don't. You create a second "marker" release whose only purpose is to announce to the world that this release is bad.

Example:

Current release list:

    ...
    2.2019.12.18.1
    2.2019.12.19.1-n
    2.2019.12.19.2
    2.2020.01.01.3-bd

Bad release you can't yank: 2.2020.01.01.3-bd

Create a new marker release: 2.2020.01.01.3-z

New release list:

    ...
    2.2019.12.18.1
    2.2019.12.19.1-n
    2.2019.12.19.2
    2.2020.01.01.3-bd
    2.2020.01.01.3-z

Now everyone knows that 2.2020.01.01.3 is bad but couldn't be yanked.

[ Parent | on HN ]