> Normaly, if you are working in a set of spark charts, your work will spawn
> > over some weeks. So if you work directly on develop, you should not > commit > > your work to SVN until is done because you will make "develop" unstable > > until you close the feature. > Interesting, that's a different definition of "unstable" than I was > thinking. One of the goals I think folks had was to get stuff out of their > whiteboards and into a shared working environment sooner so more folks > would > notice it and it would get better faster. Requiring everyone to work in > their own branches until "complete" seems overly restrictive. > > A committer is free to decide what is unstable and what is complete. Fast branching gives us the flexibility of sharing unstable features with others, while keeping develop and master as stable as possible. The current 'whiteboard' concept is not a real alternative because it forces comitters to work on single features at one time. I will not be able to experiment with core Mustella/FlexUnit/UIComponent and work on a new component at the same time in my whiteboard. It causes me to needlessly serialize my work. Om
