Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I decided to use calendar versioning for our companies internal ERP system since it makes it explicit to end users when a new release has been rolled out (2018-06-06.1 is more human than #9b867341 or 27.1.321.1).

No reason other than that.

I also change the background image of the login page on 'major' releases where significant new features are added as a subtle visual cue that users should go check out the change log.

It's often the little touches that have a disproportionate impact on user engagement.



> 2018-06-06.1

What is the trailing 1? Are you doing multiple releases per day? Is an emergency bug fix release on June 8th 2018-06-08.1 or 2018-06-06.2?


Yep, multiple releases per day if there is a nasty bug/regression.

It's rare but it happens.

I chose to start at .1 and not .0 because users don't really get 0-based releases (at least mine don't).




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: