imjoey commented on pull request #1249: URL: https://github.com/apache/apisix-dashboard/pull/1249#issuecomment-757088037
@juzhiyuan IMHO, the cherry-pick work will not cost too much time if we can keep the release cycle as short as possible, especially with a time plan. For example, once getting started for a new release, we could checkout a new release branch and froze features, as well as make the configurations and CI ready for the release branch. Then in the next few days, only bug fixes affected this release would be cherry picked from master branch. During this period, we should keep an eye on every single issue and PR to determine if it's related to the new release. Honestly, I've no idea if there any specific release flow limit as an Apache project. So looking forward to your insights that I can learn a lot from you. Thanks. ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
