Re: 4D dot releases versus R releases - a metaphor

[Robert McKeever via 4D_Tech]

No, it’s just Friday…

> On Sep 8, 2017, at 7:20 AM, David Adams via 4D_Tech <4d_tech@lists.4d.com> 
> wrote:
> 
> On Fri, Sep 8, 2017 at 11:41 PM, Doug Hall via 4D_Tech <4d_tech@lists.4d.com
>> wrote:
> 
>> What's wrong with using semantic versioning, like the rest of the entire
>> freaking world?
>> 
> 
> Wait, are you saying that just because something has been confusing for
> years, offers no obvious benefits to anyone, and is unlike common practice
> that 4D should change it? Huh, concept.
> **
> 4D Internet Users Group (4D iNUG)
> FAQ:  http://lists.4d.com/faqnug.html
> Archive:  http://lists.4d.com/archives.html
> Options: http://lists.4d.com/mailman/options/4d_tech
> Unsub:  mailto:4d_tech-unsubscr...@lists.4d.com
> **

_
Bob McKeever  http://www.mswl.com 
McKeever's Software Wizardry
Port Coquitlam, B.C.
bobmckee...@mac.com




**
4D Internet Users Group (4D iNUG)
FAQ:  http://lists.4d.com/faqnug.html
Archive:  http://lists.4d.com/archives.html
Options: http://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:4d_tech-unsubscr...@lists.4d.com
**

Re: 4D dot releases versus R releases - a metaphor

[David Adams via 4D_Tech]

On Fri, Sep 8, 2017 at 11:41 PM, Doug Hall via 4D_Tech <4d_tech@lists.4d.com
> wrote:

> What's wrong with using semantic versioning, like the rest of the entire
> freaking world?
>

Wait, are you saying that just because something has been confusing for
years, offers no obvious benefits to anyone, and is unlike common practice
that 4D should change it? Huh, concept.
**
4D Internet Users Group (4D iNUG)
FAQ:  http://lists.4d.com/faqnug.html
Archive:  http://lists.4d.com/archives.html
Options: http://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:4d_tech-unsubscr...@lists.4d.com
**

Re: 4D dot releases versus R releases - a metaphor

[Chip Scheide via 4D_Tech]

exactly...
can't be the asme  (same)

:)


On Fri, 8 Sep 2017 08:41:01 -0500, Doug Hall via 4D_Tech wrote:
> What's wrong with using semantic versioning, like the rest of the entire
> freaking world?
---
Gas is for washing parts
Alcohol is for drinkin'
Nitromethane is for racing 
**
4D Internet Users Group (4D iNUG)
FAQ:  http://lists.4d.com/faqnug.html
Archive:  http://lists.4d.com/archives.html
Options: http://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:4d_tech-unsubscr...@lists.4d.com
**

Re: 4D dot releases versus R releases - a metaphor

[Doug Hall via 4D_Tech]

What's wrong with using semantic versioning, like the rest of the entire
freaking world?

On Thu, Sep 7, 2017 at 7:44 PM, Lee Hinde via 4D_Tech <4d_tech@lists.4d.com>
wrote:

> Not to drill too deeply, but no new features != no new changes. 16.2 for
> instance updates the Xerces engine, which apparently changed the case
> sensitivity of existing XML commands.
>
> And I think the company line is that R releases (the non-beta ones) are
> customer ready.
>
> But generally, yes, the R releases have been presented as warm ups to the
> next X.0 release. I.e, v 16 R(the last one)  = v 17
>
> > On Sep 7, 2017, at 5:37 PM, David Adams via 4D_Tech <
> 4d_tech@lists.4d.com> wrote:
> >
> > This new keyboard is just killing me. Anyway, ignore the incomplete
> version
> > of this method.
> >
> > I was reminded yesterday that it's pretty easy not to understand the
> > difference between dot releases and R releases. I guess it's the
> numbering?
> > I do understand it now (it took a few years), but it's still hard to
> > explain. I though of a new way so I'm tossing out two explanation.s
> >
> > Dot releases
> > 16.0  16.1   16.2  etc.
> > These are all incremental versions of 16.0. *No new features*, just bug
> > fixes.
> >
> > 16 R216 R3   16 R4
> > These are 16.0+ bug fixes +new features.
> >
> > New features do *not* go into dot releases, they *only* go into R
> releases.
> > 16.x is feature set for its entire lifetime, only bug fixes are added.
> >
> > Okay, that's the basic story but what hit me yesterday is that it might
> > help to think of R releases in a different way:
> >
> > 17 B1   17 B2   17 B3
> >
> > Let me say right away that this is *not* accurate. They're not really
> quite
> > betas, but if you're thinking about it from the features point of view,
> > only dot releases ended in 0 get new features. So, in this sense, R
> > releases are beta releases of *features* for the next whole number dot
> > release.
>
>
>
> **
> 4D Internet Users Group (4D iNUG)
> FAQ:  http://lists.4d.com/faqnug.html
> Archive:  http://lists.4d.com/archives.html
> Options: http://lists.4d.com/mailman/options/4d_tech
> Unsub:  mailto:4d_tech-unsubscr...@lists.4d.com
> **
>
**
4D Internet Users Group (4D iNUG)
FAQ:  http://lists.4d.com/faqnug.html
Archive:  http://lists.4d.com/archives.html
Options: http://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:4d_tech-unsubscr...@lists.4d.com
**

Re: 4D dot releases versus R releases - a metaphor

[Lee Hinde via 4D_Tech]

Not to drill too deeply, but no new features != no new changes. 16.2 for 
instance updates the Xerces engine, which apparently changed the case 
sensitivity of existing XML commands.

And I think the company line is that R releases (the non-beta ones) are 
customer ready.

But generally, yes, the R releases have been presented as warm ups to the next 
X.0 release. I.e, v 16 R(the last one)  = v 17 

> On Sep 7, 2017, at 5:37 PM, David Adams via 4D_Tech <4d_tech@lists.4d.com> 
> wrote:
> 
> This new keyboard is just killing me. Anyway, ignore the incomplete version
> of this method.
> 
> I was reminded yesterday that it's pretty easy not to understand the
> difference between dot releases and R releases. I guess it's the numbering?
> I do understand it now (it took a few years), but it's still hard to
> explain. I though of a new way so I'm tossing out two explanation.s
> 
> Dot releases
> 16.0  16.1   16.2  etc.
> These are all incremental versions of 16.0. *No new features*, just bug
> fixes.
> 
> 16 R216 R3   16 R4
> These are 16.0+ bug fixes +new features.
> 
> New features do *not* go into dot releases, they *only* go into R releases.
> 16.x is feature set for its entire lifetime, only bug fixes are added.
> 
> Okay, that's the basic story but what hit me yesterday is that it might
> help to think of R releases in a different way:
> 
> 17 B1   17 B2   17 B3
> 
> Let me say right away that this is *not* accurate. They're not really quite
> betas, but if you're thinking about it from the features point of view,
> only dot releases ended in 0 get new features. So, in this sense, R
> releases are beta releases of *features* for the next whole number dot
> release.



**
4D Internet Users Group (4D iNUG)
FAQ:  http://lists.4d.com/faqnug.html
Archive:  http://lists.4d.com/archives.html
Options: http://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:4d_tech-unsubscr...@lists.4d.com
**

Re: 4D dot releases versus R releases - a metaphor

[David Adams via 4D_Tech]

This new keyboard is just killing me. Anyway, ignore the incomplete version
of this method.

I was reminded yesterday that it's pretty easy not to understand the
difference between dot releases and R releases. I guess it's the numbering?
I do understand it now (it took a few years), but it's still hard to
explain. I though of a new way so I'm tossing out two explanation.s

Dot releases
16.0  16.1   16.2  etc.
These are all incremental versions of 16.0. *No new features*, just bug
fixes.

16 R216 R3   16 R4
These are 16.0+ bug fixes +new features.

New features do *not* go into dot releases, they *only* go into R releases.
16.x is feature set for its entire lifetime, only bug fixes are added.

Okay, that's the basic story but what hit me yesterday is that it might
help to think of R releases in a different way:

17 B1   17 B2   17 B3

Let me say right away that this is *not* accurate. They're not really quite
betas, but if you're thinking about it from the features point of view,
only dot releases ended in 0 get new features. So, in this sense, R
releases are beta releases of *features* for the next whole number dot
release.
**
4D Internet Users Group (4D iNUG)
FAQ:  http://lists.4d.com/faqnug.html
Archive:  http://lists.4d.com/archives.html
Options: http://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:4d_tech-unsubscr...@lists.4d.com
**

4D dot releases versus R releases - a metaphor

[David Adams via 4D_Tech]

I was reminded yesterday that it's pretty easy not to understand the
difference between dot releases and R releases. I guess it's the numbering?
I do understand it now (it took a few years), but it's still hard to
explain. I though of a new way so I'm tossing out two explanation.s

16.016.1
16.2
**
4D Internet Users Group (4D iNUG)
FAQ:  http://lists.4d.com/faqnug.html
Archive:  http://lists.4d.com/archives.html
Options: http://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:4d_tech-unsubscr...@lists.4d.com
**