Hi, > we should only share things with great potential to be merged in develop.
Seems reasonable to me - but it may become a bit of a mess if we are not careful. More questions for the wiki that need an answer: How do we avoid the big bang integration issues that occur with this model? For instance making 4.9 was a huge pain having to merge in all the changes that had occurred since 4.8, I would hate to have to do that with 20 or 30 branches. If we have a large number of branches is it the release managers job to merge them all or the person who created the branch, what if they are no longer about? How do we prune branches that are no longer actively been worked on? Thanks, Justin
