You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As Sentinel 2.0 is planned to be a nouveau version that includes traffic governance, we will need to maintain parallel evolution of both the 2.0 series and the 1.8 series for a period of time. To facilitate this, we propose to introduce a branching model that supports parallel development: using the development branch for the 1.8 series as the main branch, and the development branch for the 2.0 series as the parallel development branch. Contributors will choose the appropriate branch to merge their features based on the domain to which the features belong. We will regularly synchronize the commits from the main branch to the parallel development branch. This parallel development model will continue until multiple stable versions of the 2.0 series have been released. If anyone has any suggestions for the current design of this branching model, or has a better branching model to meet the needs of parallel evolution, welcome to join the discussion!
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
由于 Sentinel 2.0 计划是包含了流量治理的全新版本,所以在一段时间内我们需要保持 2.0 系列以及 1.8 系列的并行演进。为此,我们希望引入能够支撑并行开发的分支模型:将 1.8 系列的开发分支作为主分支, 2.0 系列的开发分支作为并行开发分支,贡献者根据功能所属领域选择合入的分支。我们会定期将主分支上的提交同步到并行开发分支上。这种并行开发模式将持续到 2.0 系列完成多个稳定版本的发布。大家对于目前设计的这种分支模型有任何建议,或者有没有什么更好的分支模型来满足并行演进的需求,欢迎参与讨论!
As Sentinel 2.0 is planned to be a nouveau version that includes traffic governance, we will need to maintain parallel evolution of both the 2.0 series and the 1.8 series for a period of time. To facilitate this, we propose to introduce a branching model that supports parallel development: using the development branch for the 1.8 series as the main branch, and the development branch for the 2.0 series as the parallel development branch. Contributors will choose the appropriate branch to merge their features based on the domain to which the features belong. We will regularly synchronize the commits from the main branch to the parallel development branch. This parallel development model will continue until multiple stable versions of the 2.0 series have been released. If anyone has any suggestions for the current design of this branching model, or has a better branching model to meet the needs of parallel evolution, welcome to join the discussion!
Beta Was this translation helpful? Give feedback.
All reactions