name FreeCAD 0.91 instead of 0.20, means version after 0.19 could be 0.91

Have some feature requests, feedback, cool stuff to share, or want to know where FreeCAD is going? This is the place.
Forum rules
Be nice to others! Read the FreeCAD code of conduct!
User avatar
Joel_graff
Posts: 1537
Joined: Fri Apr 28, 2017 4:23 pm
Contact:

Re: name FreeCAD 0.91 instead of 0.20, means version after 0.19 could be 0.91

Postby Joel_graff » Fri Mar 29, 2019 2:23 pm

I remember reading somewhere that using a year-based versioning scheme could create issues for Debian packaging or something... No idea why / how, but it's something to consider.
FreeCAD Trails workbench for transportation engineering: https://www.github.com/joelgraff/freecad.trails

pivy_trackers 2D coin3D library: https://www.github.com/joelgraff/pivy_trackers
User avatar
kkremitzki
Posts: 1757
Joined: Thu Mar 03, 2016 9:52 pm
Location: Texas

Re: name FreeCAD 0.91 instead of 0.20, means version after 0.19 could be 0.91

Postby kkremitzki » Fri Mar 29, 2019 3:16 pm

How 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.
Like my FreeCAD work? I'd appreciate any level of support via Patreon, Liberapay, or PayPal! Read more about what I do at my blog.
Mark Szlazak
Posts: 405
Joined: Tue Apr 04, 2017 6:06 pm
Location: Edmonton, Canada

Re: name FreeCAD 0.91 instead of 0.20, means version after 0.19 could be 0.91

Postby Mark Szlazak » Fri Mar 29, 2019 6:08 pm

kkremitzki wrote:
Fri Mar 29, 2019 3:16 pm
How 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.
I do not understand how 1.0 or 2.0 tells me whether i am using a current version not??
User avatar
Zolko
Posts: 390
Joined: Mon Dec 17, 2018 10:02 am

Re: name FreeCAD 0.91 instead of 0.20, means version after 0.19 could be 0.91

Postby Zolko » Fri Mar 29, 2019 6:31 pm

Mark Szlazak wrote:
Fri Mar 29, 2019 6:08 pm
I do not understand how 1.0 or 2.0 tells me whether i am using a current version not??
you're really a helpless lot: 1.0 is cool, and 2.0 is futuristic. geeez ... didn't you learn anything in engineering school ?
try the Assembly4 workbench for FreCAD v0.19
installable with Tools > Addon Manager, new version 0.7. Simple tutorial here
User avatar
Zolko
Posts: 390
Joined: Mon Dec 17, 2018 10:02 am

Re: name FreeCAD 0.91 instead of 0.20, means version after 0.19 could be 0.91

Postby Zolko » Fri Mar 29, 2019 6:41 pm

wmayer wrote:
Tue Mar 26, 2019 9:38 pm
friendly and constructive manner until Zolko and you joined it
sure ... a nice scape-goat you have here....
try the Assembly4 workbench for FreCAD v0.19
installable with Tools > Addon Manager, new version 0.7. Simple tutorial here
User avatar
Joel_graff
Posts: 1537
Joined: Fri Apr 28, 2017 4:23 pm
Contact:

Re: name FreeCAD 0.91 instead of 0.20, means version after 0.19 could be 0.91

Postby Joel_graff » Fri Mar 29, 2019 6:59 pm

Zolko wrote:
Fri Mar 29, 2019 6:31 pm
you're really a helpless lot: 1.0 is cool, and 2.0 is futuristic. geeez ... didn't you learn anything in engineering school ?
I'm really not at all sure what that's supposed to mean.

The value of moving to version 1.0 is primarily for public relations. It signals to others that our project is one that has matured and has considerable value to it's users - and there's plenty of evidence to be found both here and outside our community that demonstrates these things are true.

In the end, though, it's really only a number. It has no intrinsic value beyond indicating a progression in development.
FreeCAD Trails workbench for transportation engineering: https://www.github.com/joelgraff/freecad.trails

pivy_trackers 2D coin3D library: https://www.github.com/joelgraff/pivy_trackers
User avatar
Zolko
Posts: 390
Joined: Mon Dec 17, 2018 10:02 am

Re: name FreeCAD 0.91 instead of 0.20, means version after 0.19 could be 0.91

Postby Zolko » Fri Mar 29, 2019 7:02 pm

wmayer wrote:
Wed Mar 27, 2019 9:30 am
As far as I remember from discussions with Jürgen the plan to switch to version 1.0 was when the most important issues are solved:
it's the topological naming as you said and the assembly workbench.
I don't know about Jürgen, but that seems quite logical today.

so... how about App::Link ? Is this the goal for v0.19 ? (or any next version) ?
try the Assembly4 workbench for FreCAD v0.19
installable with Tools > Addon Manager, new version 0.7. Simple tutorial here
User avatar
bernd
Posts: 8414
Joined: Sun Sep 08, 2013 8:07 pm
Location: Zürich, Switzerland

Re: name FreeCAD 0.91 instead of 0.20, means version after 0.19 could be 0.91

Postby bernd » Fri Mar 29, 2019 7:10 pm

kkremitzki wrote:
Fri Mar 29, 2019 3:16 pm
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
yes, yes, yes, jm2c
User avatar
kkremitzki
Posts: 1757
Joined: Thu Mar 03, 2016 9:52 pm
Location: Texas

Re: name FreeCAD 0.91 instead of 0.20, means version after 0.19 could be 0.91

Postby kkremitzki » Fri Mar 29, 2019 7:14 pm

Mark Szlazak wrote:
Fri Mar 29, 2019 6:08 pm
I do not understand how 1.0 or 2.0 tells me whether i am using a current version not??
Strictly speaking a year.month version doesn't tell you if it's current or not, either, just if it's recent.

bernd wrote:
Fri Mar 29, 2019 7:10 pm
yes, yes, yes, jm2c
Your third yes is in response to a either/or question.
Like my FreeCAD work? I'd appreciate any level of support via Patreon, Liberapay, or PayPal! Read more about what I do at my blog.
Mark Szlazak
Posts: 405
Joined: Tue Apr 04, 2017 6:06 pm
Location: Edmonton, Canada

Re: name FreeCAD 0.91 instead of 0.20, means version after 0.19 could be 0.91

Postby Mark Szlazak » Fri Mar 29, 2019 7:34 pm

kkremitzki wrote:
Fri Mar 29, 2019 7:14 pm
Mark Szlazak wrote:
Fri Mar 29, 2019 6:08 pm
I do not understand how 1.0 or 2.0 tells me whether i am using a current version not??
Strictly speaking a year.month version doesn't tell you if it's current or not, either, just if it's recent.
Yes that is what i said. Which means it is more information than version numbers like 1.0, etc.