Hi, > The point is that it is generally considered bad form to work directly in > the 'master' branch. But not to the point of avoiding it altogether and merging as infrequently as the flex project does.
> Provided that you a valid reason. Here's several - there's probably more: 1. People accidentally working in the wrong branch (has happened several times). 2. User confusion about where to get the latest code (has happened many times). 3. External tools assume master is default branch by default and give wrong or confusing picture of the state of the project (eg github). 4. Outside perception is not much is happen as master branch is more visible than develop (can point to several instances of this). 5. Not in line with advice of mentors. 6. Not in line with other Apache projects. 7. Extra work for release manager. 8. Potential merge issues (see issues with 4.9.1 merge). 9. Huge gap between master and develop means users can't apply patches and are either forced to live with bugs or risk using develop branch (releasing more often would help this). Thanks, Justin
