Hi all. SeaTunnel version 2.3.x has gradually become stable, and many users are starting to use version 2.3.x. We will start the development of the next big feature soon. The new feature may cause instability due to a large number of changes.
How do we manage the development branch of the Feature and the disbursement of bug fixes? If new features and bug fixes are maintained in the dev branch, it may result in bug fixes and new features being synchronized with the third version number, and new features may introduce new bugs. Version 2.3 will be difficult to truly stabilize. However, if our third version number only contains bug fixes, and all bug fixes are made from the 2.3. x release branch (like the Apache Dolphin Scheduler), then we need to maintain the release branch for how long. The same bug may require different fixes in different branches, which seems difficult for developers. Do we have a better way to manage bug fixes and the development of new features? -- Best Regards ------------ EricJoy2048 [email protected]
