On 2013-03-04 at 21:57:41 [+0100], Clemens <clemens.zeidler@xxxxxxxxx>
wrote:
fully agree. However, I have the feeling it is harder do that in the
main
branch. At the moment it might be easier but when it comes to a release
it
will become hard again. A second branch would be helpful to try stuff
out,
i.e. things that not can be developed entirely in a branch. For example,
the last window management discussion (maximizing, resizing, zooming...)
One can implement such stuff in a branch but if nobody is using and
trying
it, its pointless. There must be some user feedback like: "this feature
is
good, the other one is useless/annoying..."
You can do this as an extra decorator, without branching at all. Just the
same way Stack and Tile was developed. Or you can do it in your own
branch
and make a binary package that people can try out. Looncraz does that on
our mailing lists and he seems to get some useful answers.
I see the point that much stuff can be done in the main branch, but some
testing stuff just do not fit there. I'm also not fixed on a R2 branch
but
some platform to do research on new stuff would be good. A R2 branch
would
have the advantage that all R2 developers automatically become guinea
pigs
;-) Furthermore, official nighties would make it easier for
non-developers. Hope you got the idea...
This essentially means less people working in the R1 branch. This is a
good
way to let that branch aside. By enforcing everyone to work on the same
branch, we enforce several things :
- People try not to completely break the build with their changes.
Either
working in their own branch, or not enabling their WIP code to be
included
in the image.
- Developers stay focused towards the R1 goal. Even if sometimes it's
fun
or motivating to work on newer features, it's important to keep an eye on
the release target. And there are a lot of bugs we should fix before R1
can
happen
