I would like that. We can be liberal backporting changes to the 4.1
release, but some care should be taken to avoid very big or risky
changes. Then for the 4.2 release candidates, ideally only bugfixes
would be backported.
On 9/15/23 22:51, Gerald Combs wrote:
I have no objections to creating
I have no objections to creating the 4.2 branch earlier. As you point out, it mostly
comes down to how much backporting we want to do. The release numbers are a reflection of
the fact that "run tools/make-version.py -v ..." is in the new release branch
checklist.
On 9/15/23 12:06 PM, João Valv
Should 4.1 be developed on the release-4.2 branch already? Obviously it
would require some backporting work from developers, but also provide
some stability. Right now the 4.1 release is just a snapshot of master,
so really 4.1.x micro versions are meaningless.
There are some changes that migh
