Chronologic Versioning: No more arbitrary version updates and regressions

Re:Chronologic Versioning: No more arbitrary version updates... by jacquesm on Thursday January 02, 2020 @03:28AM (#21933779)

Totally agreed. This is seriously overthought. Users need to be able to tell in an eyeblink what the order is without reference to some standards document. Presumably everybody to whom it applies can count.

[ Parent | on HN ]

Re:Chronologic Versioning: No more arbitrary version updates... by true_religion on Thursday January 02, 2020 @05:48AM (#21934347)

For a web app under continuous release, I would suggest doing both.

230-12-01-2020 to mean the 230th release since the start of the project, made on January 1st, 2020.

[ Parent | on HN ]

Re:Chronologic Versioning: No more arbitrary version updates... by oneeyedpigeon on Thursday January 02, 2020 @07:06AM (#21934720)

Why not 230-2020-12-01 to avoid the awkward 'US order or 'most-of-the-rest-of-the-world order' issue?

Edit: the great irony is that your example included an error which I then reproduced! Obviously, 1st jan is unambiguously:

230-2020-01-01

If you were representing 1st dec, though, I’d suggest:

230-2020-12-01

[ Parent | on HN ]

Re:Chronologic Versioning: No more arbitrary version updates... by true_religion on Friday January 03, 2020 @02:56AM (#21944094)

Actually I was trying to avoid the US date standard myself, then got confused and wrote a date that follows no standard that I know of. My mistake entirely.

[ Parent | on HN ]

Re:Chronologic Versioning: No more arbitrary version updates... by BuildTheRobots on Thursday January 02, 2020 @08:54AM (#21935332)

230-12-01-2020 to mean the 230th release since the start of the project, made on January 1st, 2020.

Surely this is either released on the first of December or the 12th of January?

[ Parent | on HN ]

Re:Chronologic Versioning: No more arbitrary version updates... by de_watcher on Thursday January 02, 2020 @10:26AM (#21936092)

That's just US date trolling.

[ Parent | on HN ]