2 ms·
The example I gave on the site with "UI and implementation" branches could work. I haven't done this in practice so I cannot confirm. Idk how you'd be able to
by NetOpWibby 7y ago
The example I gave on the site with "UI and implementation" branches could work. I haven't done this in practice so I cannot confirm.
Idk how you'd be able to tell anything about a commit from its hash tbh.
You're right though, I primarily create/work on SaaS products and this versioning is perfect for it.
- saxonww 7y agoI think my original reply was a little brusque. Really this is a fine scheme, but I do think it's limited in where it can realistically be used - IMO, small self-contained SaaS products only - and I do think that the hash should be called out explicitly as metadata vs. an integral part of the version. Simply moving from YEAR.MONTH.DAY.CHANGE_ID to YEAR.MONTH.DAY.UPDATE.CHANGE_ID, with UPDATE being a mandatory monotonically-increasing integer, would make this scheme more attractive to a wider variety of users.