That should be documented in “How to Cook a Release”
Patricia
> On Mar 28, 2021, at 09:36, Marcus wrote:
>
> Am 28.03.21 um 17:39 schrieb Carl Marcum:
>>> On 3/28/21 11:02 AM, Marcus wrote:
>>> Am 28.03.21 um 16:14 schrieb Carl Marcum:
I'm wondering if we should create a branch we can
Am 28.03.21 um 17:39 schrieb Carl Marcum:
On 3/28/21 11:02 AM, Marcus wrote:
Am 28.03.21 um 16:14 schrieb Carl Marcum:
I'm wondering if we should create a branch we can use for
continuation of the 4.1.x line to have a place to PR cherry-picks,
bug fixes, etc. in case we need another release
Hi Marcus,
On 3/28/21 11:02 AM, Marcus wrote:
Am 28.03.21 um 16:14 schrieb Carl Marcum:
I'm wondering if we should create a branch we can use for
continuation of the 4.1.x line to have a place to PR cherry-picks,
bug fixes, etc. in case we need another release on that line.
IMHO we have
Am 28.03.21 um 16:14 schrieb Carl Marcum:
I'm wondering if we should create a branch we can use for continuation
of the 4.1.x line to have a place to PR cherry-picks, bug fixes, etc. in
case we need another release on that line.
IMHO we have already agreed in the past that we want to create a
Hi All,
I'm wondering if we should create a branch we can use for continuation
of the 4.1.x line to have a place to PR cherry-picks, bug fixes, etc. in
case we need another release on that line.
For instance I've got a number of commits (about 26) I've cherry picked
mostly from Damjan's
