I do not understand how 1.0 or 2.0 tells me whether i am using a current version not??kkremitzki wrote: ↑Fri Mar 29, 2019 3:16 pmHow often does one really need to say, version X was this long ago? All that seems to matter to me is to know the current version, and to be able to say whether a version is older than current. I'm not a fan of year.date versioning systems because doesn't allow you to communicate the significance of the changes in a new version, just that it's newer, but dotted decimal versions can do that too. It also keeps our tie to yearly releases, which IMO we should view as a historical coincidence... having huge gaps of time between releases doesn't help us get any better at making releases.
Also, there are actually several issues being discussed here:
1. should we drop the leading 0 in the version to communicate FreeCAD's maturity (and stop communicating its immaturity)
2. should we have a 1.0 release to communicate FreeCAD's readiness for wide usage
3. should we use a major.minor.patch or year.date versioning system
It seems the consensus to 1 is 'yes'. The arguments for 2 are strong--not having a 1.0 release is like not having a graduation ceremony. Deciding on 3 can IMO be deferred after we drop the leading 0 and after we have a 1.0 release--it's a separate issue.
Also, I don't think a year.date versioning system would cause any Debian packaging problems, except that if we switch to it we can't easily switch back, which seems unlikely anyway.
you're really a helpless lot: 1.0 is cool, and 2.0 is futuristic. geeez ... didn't you learn anything in engineering school ?Mark Szlazak wrote: ↑Fri Mar 29, 2019 6:08 pmI do not understand how 1.0 or 2.0 tells me whether i am using a current version not??
sure ... a nice scape-goat you have here....
I'm really not at all sure what that's supposed to mean.
I don't know about Jürgen, but that seems quite logical today.
yes, yes, yes, jm2ckkremitzki wrote: ↑Fri Mar 29, 2019 3:16 pm1. should we drop the leading 0 in the version to communicate FreeCAD's maturity (and stop communicating its immaturity)
2. should we have a 1.0 release to communicate FreeCAD's readiness for wide usage
3. should we use a major.minor.patch or year.date versioning system
Strictly speaking a year.month version doesn't tell you if it's current or not, either, just if it's recent.Mark Szlazak wrote: ↑Fri Mar 29, 2019 6:08 pmI do not understand how 1.0 or 2.0 tells me whether i am using a current version not??
Your third yes is in response to a either/or question.
Yes that is what i said. Which means it is more information than version numbers like 1.0, etc.kkremitzki wrote: ↑Fri Mar 29, 2019 7:14 pmStrictly speaking a year.month version doesn't tell you if it's current or not, either, just if it's recent.Mark Szlazak wrote: ↑Fri Mar 29, 2019 6:08 pmI do not understand how 1.0 or 2.0 tells me whether i am using a current version not??