adopt more traditional version labeling about 4d-netkit HOT 4 CLOSED

I understand the point and I somewhat agree
We use another VCS before Git and we keep this flat way to proceed.

For my component until there is no real change, I synchronise my 20R. branch with the main. But I am the only one.
So cherry pick is the norm. (we have some tools in our BugBase tool to create merge request easily)

from 4d-netkit.

Component branch follow strictly 4D one to not fall into dependency hell and to follow R release train (3 months) with chosen and tested features

This component branch 20R5 is for 4D 20R5 (soon in beta after some tests before releasing, maybe it run, but not fully re-tested)
Main is already for 20R6 (and not stable with new features)

And as 4D component dev (not this one) we could use new language features by branch (for instance "Try Catch" or other things that could not work in previous release)

from 4d-netkit.

the thing i'm thinking about are when hotfixes, like PR63 hit (assuming that it is accepted), they might need to be applied to multiple versions.
since netkit is supposed to be an internal component, i get lining it up with the branches. it just seems like more work to have to cherrypick hotfixes onto each of the supported branches.

from 4d-netkit.

on, that's right. i forgot you guys didn't use git for everyday tasks.
nothing to see here. move along.

from 4d-netkit.