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
Currently we create development branch for all projects to make sure the code development would not affect the stability of master branch, but since we have published several releases (especially Capri release), in fact this development pattern is more and more becoming a burden for developers to maintain the project, especially when committers need to publish the new release. So I suggest we could remove development branch so all PRs can directly be merged into master branch.
I am in favor of removing the development branch, but we should wait until we discussed about it in the next TSC meeting (which is next week) and also in the next week's OpenSDS Technical meeting before making this change. We need to give people enough time to move their code over.
We should merge Fujitsu's driver before making this change. Please note that Fujitsu's driver should be backported to stable/capri. However I noticed that stable/capri is not cut yet. We should cut stable/capri first.
Cut stable/capri
Announce the removal of development branch in the next TSC and Technical Meeting. Also mention it on OpenSDS slack channel.
Merge Fujitsu driver and backport to stable/capri (We should only cherry-pick this driver commit).
After Fujitsu driver is merged, ask all open PR authors to submit their PR to master directly.
Send a notification email to OpenSDS tech-discuss mailing list and other mailing list.
Got it, thanks for that. BTW, stable/capri branch has been set for all projects except orchestration and anomoly-detection, @xing-yang could u help finish it? Thanks!
Currently we create
development
branch for all projects to make sure the code development would not affect the stability ofmaster
branch, but since we have published several releases (especially Capri release), in fact this development pattern is more and more becoming a burden for developers to maintain the project, especially when committers need to publish the new release. So I suggest we could remove development branch so all PRs can directly be merged into master branch.@stevenphtan @xing-yang @skdwriting @rakeshJn Any thoughts?
The text was updated successfully, but these errors were encountered: