News for hackers. Stuff that matters.
Re:German tank problem by vacri on Friday February 21, 2014 @08:23PM (#7280559)
Just name the hotfixes by day (140222). It monotically increases, and if you do multiple hotfixes in one day, suffix a/b/c etc. Generally you're unlikely to get up to b or c, and there's no clue to how many previous versions there's been.
Re:German tank problem by hcarvalhoalves on Friday February 21, 2014 @10:33PM (#7280887)
Drop the a,b,c... just timestamp it.
Re:German tank problem by vacri on Saturday February 22, 2014 @04:37AM (#7281562)
Leads to longer timestamps though, when you include the HHMM. If you're generally not doing more than one per day, this makes it a little easier - usually six digits instead of ten.
Re:German tank problem by mseebach on Saturday February 22, 2014 @06:04AM (#7281733)
If only we had access to some kind of machine that made dealing with long numbers easy.
Re:German tank problem by vacri on Saturday February 22, 2014 @07:55AM (#7281940)
Except that a hotfix number is a human-interaction number, not an automation device. Speaking as someone who has worked on the support phones, I'd much, much, much rather someone only have to read back a six-digit number than a ten-digit one.
Re:German tank problem by T-hawk on Saturday February 22, 2014 @11:25AM (#7282511)
That was proposed (with a numeric suffix rather than letter), but rejected because we often would do 3 to 5 in a day, and somebody decided that would still leak too much information about our hotfix workflow. Another aspect would be that hotfixes would sometimes go several days between packaging and deployment (for all your usual megacorp red-tapey risk-aversey reasons), and we didn't want to explain to clients why 20120214 wasn't deployed until 2012-02-21.