Brian Aker wrote: > Hi! > > Thanks to everyone who responded to this thread. After reading > everything I believe the best choice is this: > > YEAR.MONTH.BZR_REVISION
Sounds great. I've got a patch to integrate this into autoconf et. al. Since the numbers are all derived, it means we won't have that chicken-and-egg problem of when do you increment the number and then commit it into the configure.ac file. > This gives us a lot of information: > 1) Someone can have an idea of how old their tree is vs someone else's > at a glance. > 2) Developers can pull and get exactly the correct revision. And if > someday we move to another system? We don't mess up our history. > > I especially appreciated the comments about ALPAH/BETA/etc. To me those > have always been more about marketing then anything else. We aren't in > the distribution business, so we can leave that to those who are. > > Version numbers have long since become the domain of marketing folk, > which really is fine. I think we can skip this though for the time being > for ourselves. > > Any further comments? Well, I hate that version numbers have been taken over by marketing folks, but I think that schemes like this help move them back to being based on actual information. Monty _______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
