[Bf-committers] RFC: "Continuous integration" branch?

Sergey Sharybin sergey.vfx at gmail.com
Thu Mar 5 23:42:15 CET 2015

Hey guys,

I know it's really a double-edged sword, but still. What about having
branch which:

- Called somewhat clear what it is: like continous_integration (not the
best name in the world perhaps)
- It allows developers to commit stuff, regardless of the BCon level
- Mainly used dugin bcon3 and bcon4 for the work which can't go to master
just because because of bcon.
- All the commits to this branch are considered master-ready, no
WIP/experimental work in there is allowed
- Get;s merged into master after git is open
- No commits happening t bcon1,2
- Naming could be improved

Mainly motivation is coming from:

- We're now trying to spend more time on patch reviews, and there are some
good patches which are ready for commit but can't go in because of BCon
- Leaving those patches open might lead to situation when we'll loose it
from the field of view and wouldn't commit during bcon1,2
- There're some ongoing improvements from all the guys around, not just
core developers and would be nice if those patches are not getting rottened
or so
- All the devs are still free to work on the "fun" projects, and could have
some stuff cooked during bcon3,4

While it sounds like a good idea, i'm actually a bit skeptical about it.
Mainly because i would actually prefer everyone to concentrate on making
blender stable at bcon3,4. But on the other hand, we can't force all the
volunteers to wait, plus we can do some improvements at a spare time. So it
might actually work.

This is actually a question to all the core developers: do you guys think
it might work (maybe with some tweaks to the workflow) and we should try or
it's somewhat just crazy?

There might also be some other approaches to a problem i'm trying to solve,
those are also welcome!

With best regards, Sergey Sharybin

More information about the Bf-committers mailing list