search

rancher / backup-restore-operator

Apache License 2.0
98 stars 67 forks source link

Set default ci in master branch #470

Closed alexandreLamarre closed 3 months ago

alexandreLamarre commented 4 months ago

So that newer long-lived branches can default to configurations in there.

Remove default drone CI as well.

mallardduck commented 4 months ago

I wonder if we just delete the master branch? Given that we develop on release branches, does it even make sense to use it at all? Or should we just plan to use w/e the highest release branch is to create the base for the next release branch? (I.e. release/v5.0 will become the base for release/v6.0 once we start on Rancher 2.10.x?)

Or are you thinking we use the master branch as an intermediate between releases? If so, how will we keep it in sync with the latest release branch?

ericpromislow commented 4 months ago

I assumed once we start working on rancher 2.10 (or 3.0, or whatever comes after 2.9) we'll branch release/v6.0 off of release/v5.0 and continue development there. And we can leave master for anything that wants a default branch that isn't tied to a release.