On 02/14/2018 06:21 PM, Daan Hoogland wrote:
> the -x would only add it to the comment making it harder to find. As for
> multiple stable branches; merging forward always folows all branches
> forward so a fix on 4.9 would be merged forward to 4.10 and then 4.10 would
> be merged forward again to
the -x would only add it to the comment making it harder to find. As for
multiple stable branches; merging forward always folows all branches
forward so a fix on 4.9 would be merged forward to 4.10 and then 4.10 would
be merged forward again to 4.11 and finally to master. of course there is
always
Hi Daan
On 02/14/2018 05:26 PM, Daan Hoogland wrote:
> Rene,
>
> The issue is certainly not due the git workflow but to upgrade schemes we
> have.
>
> The result of this workflow for us is that it is easier to find to which
> branches a particular commit is added as by merging forward the
Rene,
The issue is certainly not due the git workflow but to upgrade schemes we
have.
The result of this workflow for us is that it is easier to find to which
branches a particular commit is added as by merging forward the commit id
of the actual fix doesn't change. so instead of looking in each
van Rensburg
Subject: [DISCUSS] DB upgrade issue workaround for 4.10.0.0 users upgrading to
4.11.0.0
All,
Some of us have discussed and found an upgrade path issue that only affects the
4.10.0.0 users who may see missing columns in certain tables post upgrading to
4.11.0.0 version.
All,
Some of us have discussed and found an upgrade path issue that only affects the
4.10.0.0 users who may see missing columns in certain tables post upgrading to
4.11.0.0 version.
The issue is/was that at the time 4.10.0.0 was released, PRs were merged to the
'then' master branch that
