Abdelrazak Younes wrote: > One: merging will be difficult when a feature has been cooked based on > master. The main reason is that master will see a lot code refactoring > and cleanup. So, unless you accept that "code refactoring and cleanup" > branches get also merged into stable branch (which I would be OK with > personally), your model won't work and new features won't get > backported. I am pretty sure of that. But if you are as liberal as you > seem to be and if you will accept "code refactoring and cleanup" > branches to be merged, then the model will fly.
If refactoring and cleanup is put in (only) for the sake of adding new features more easily and at the cost of stability, I am not very pleased by this idea. Jürgen
