Older branches merging? #16391
-
|
Hi, I noticed that there are changes on release-0.14.2 branch that look like not merged into release-0.15.0 branch release-0.15.0...release-0.14.2 I'm not sure about that, maybe GitHub diff shows it wrongly. But usually, projects merge fixes that were made in post-release branches to main to avoid losing these fixes in the new releases. Is it normal practice for Bevy? Is it documented somewhere? Best regards, |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
From time-to-time we need to backport a fix that can't be merged cleanly due to incompatible changes that have since been merged. Those are the commits you're seeing. |
Beta Was this translation helpful? Give feedback.
From time-to-time we need to backport a fix that can't be merged cleanly due to incompatible changes that have since been merged. Those are the commits you're seeing.