On 7/19/25 2:26 AM, andy pugh wrote:
It does not make sense to push changes back to 2.9 unless you intend to release
a 2.9.5
I can't predict the future, but the policy is that bug fixes go into
2,9, and this is a bug fix.
Yes, bug fixes are usually the only thing /modified/ in stable (2.9)
branch. However, parallel bugs (in stable and master) should be patched
in master and immediately backported or fixed in stable branch and
simultaneously forward ported.
2.10 is likely to include some large changes, and so isn't feeling
imminent.
You don't want to leave bug(s) unfixed in master.
Master diverges more and more as development progresses and
(semi-)automatic (forward) merges are a serious risk due to
other/more/changed internal APIs.
Only projects that do not "develop" in master branch can easily cope
with (semi-)automatic forward porting my merging from stable branch.
--
Greetings Bertho
(disclaimers are disclaimed)
_______________________________________________
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers
