[cfe-dev] [3.5 Release] Branch Policy

[Bill Wendling]

One more things…

To ease merging the patches into the 3.5 branch, you may use the ‘utils/release/merge.sh’ script.

-bw

On Jul 22, 2014, at 9:50 AM, Bill Wendling <isanbard at gmail.com> wrote:

> Hi Developers,
> 
> This is to clarify which patches may be merged into the 3.5 branch.
> 
> * All doc changes may go in. In fact, you’re encouraged to update the branch's ReleaseNotes.rst file! :-)
> 
> * All non-documentation patches should first receive approval from the appropriate code maintainer. (A blanket approval is acceptable for the first phase of testing.)
> 
> * If your patch fixes a major bug, it may go in.
> 
> * If your patch is to complete an *existing* feature, then it may go into the 3.5 branch. However, this feature must be completed by Phase II of testing.
> 
> Once Phase II testing starts, we will be accepting only those patches that fix major bugs.
> 
> Share and enjoy!
> -bw
>