I echo Nikita's position here. With our new model, a change that happened once every year now must happen once every quarter. It would also map to our rolling release model too I believe. This was discussed in the past and we decided against it then, but now times have changed where I believe it warrants a second look. Vicențiu On Fri, 28 Jun 2024, 16:58 Nikita Malyavin via developers, < developers@lists.mariadb.org> wrote:
Hello Otto,
I think it's a good idea, which improves the quality of life.
The rebases will still have to take place, but at least the contributors won't have to update the branch names in the PR!
Regards, Nikita
On Fri, 28 Jun 2024 at 05:55, Otto Kekäläinen via developers < developers@lists.mariadb.org> wrote:
Hi!
Has the core developers had discussions about using branch name 'main' for development instead of switching to a new branch every 3 months?
If all new features and other additions would always target the branch 'main' it would lower the barrier of entry for new contributors, and decrease the number of unnecessary rebases done by contributors.
If the permanent development target was 'main', you would need to create new 11.x branches only at "freeze" when a new major version branch is cut for release.
MariaDB is currently the only open source project I know that does *not* have a main/master/trunk branch and instead does these constant new branch names. I imagine this is not only annoying for contributors, but also the core developers who waste time asking contributors to rebase PRs every 3 months (see https://github.com/MariaDB/server/pull/2556 and https://github.com/MariaDB/server/pull/2671 as examples).
- Otto _______________________________________________ developers mailing list -- developers@lists.mariadb.org To unsubscribe send an email to developers-leave@lists.mariadb.org
-- Yours truly, Nikita Malyavin _______________________________________________ developers mailing list -- developers@lists.mariadb.org To unsubscribe send an email to developers-leave@lists.mariadb.org