I pushed branch-3.4.
If the change should be part of 3.4.0 release, it must be cherry-picked to branch-3.4. 3.4.0 should be added to "Fix Versions/s" on JIRA for properly generating RELEASE NOTES.
We should not have both 3.4.0 and 3.5.0 in the field in this case. Please remove 3.5.0 if you cherry-pick the change of already fixed issues. Thanks, Masatake Iwasaki On 2025/02/19 15:19, Masatake Iwasaki wrote:
Hi Bigtop developers, I'm going to create branch-3.4 and CI jobs for 3.4.0 release. After bumping the version of master branch to 3.5.0-SNAPSHOT, committers must set "Fix Versions/s" of the JIRA issue to 3.5.0 after committing the change to master branch. If the change should be part of 3.4.0 release, it must be cherry-picked to branch-3.4. 3.4.0 should be added to "Fix Versions/s" on JIRA for properly generating RELEASE NOTES. Thanks, Masatake Iwasaki
