I once worked in a software shop where all release packages had the Unix epoch timestamp in the filename. Yes, these sorted brilliantly making it trivial to find the last one. But good luck finding a build from a specific date/time.
Considering it uses day then month, 24hr clock, and distance in km, I’m guessing the reason why it’s not “human readable in American” is because it’s intended to be “human readable for pretty much everybody else”
That’s something I think I’d like to use, but I don’t know if could get over the fact that neither the date nor the time are in ISO 8601 format.
They should put it as Unix epoch instead!
I once worked in a software shop where all release packages had the Unix epoch timestamp in the filename. Yes, these sorted brilliantly making it trivial to find the last one. But good luck finding a build from a specific date/time.
just wildcard for n digits
The date format isn’t even human readable (at least in American). It should be Sun, Jan 14th
Considering it uses day then month, 24hr clock, and distance in km, I’m guessing the reason why it’s not “human readable in American” is because it’s intended to be “human readable for pretty much everybody else”
The date format isn’t incorrect at all
I still think YYYY-MM-DD should be more apt for an international release.
IMO, that format is best for all releases.
You want to talk about sorting releases, ISO 8601 works with sorting and it’s still human readable.
My homies all start their date time stamped files with ISO 8601.
I always start my files with iso8601, except on s3 it doesn’t like the colon. Gotta replace the colons lol
Lol I came here to say this