[LLVMdev] Policy for applying fixes to released branches?
thomas.stellard at amd.com
Wed Sep 10 09:12:51 PDT 2014
On 09/10/2014 11:57 AM, Reid Kleckner wrote:
> We have one branch per point release, and we tag each micro release:
> Although I don't see 3.4.1. =/
The 3.4.1 tag is in the RELEASE_34 tag directory, we moved to the new
tag names starting with 3.4.2.
> In that case, merging to the 3.5 release branch is the correct procedure
> to get it in 3.5.1.
More information about the llvm-dev