On 10 September 2014 12:46, Roel Jordans <r.jordans at tue.nl> wrote:> Hi there, > > My guess is that such a patch should go into a new dot release becoming > 3.5.1 > > According to [1], new releases get decided on by the 'release manager', I'm > not sure who's the current person to contact for that.Tom Stellard did the previous 3.4.2 release. I'm not sure if he plans on doing any 3.5.x releases. It maybe a bit early to do a 3.5.1 release though.
Reid Kleckner
2014-Sep-10 15:57 UTC
[LLVMdev] Policy for applying fixes to released branches?
We have one branch per point release, and we tag each micro release: http://llvm.org/viewvc/llvm-project/llvm/branches/ http://llvm.org/viewvc/llvm-project/llvm/tags/ Although I don't see 3.4.1. =/ In that case, merging to the 3.5 release branch is the correct procedure to get it in 3.5.1. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20140910/8e52fc46/attachment.html>
Tom Stellard
2014-Sep-10 16:11 UTC
[LLVMdev] Policy for applying fixes to released branches?
On 09/10/2014 09:08 AM, Dan Liew wrote:> On 10 September 2014 12:46, Roel Jordans <r.jordans at tue.nl> wrote: >> Hi there, >> >> My guess is that such a patch should go into a new dot release becoming >> 3.5.1 >> >> According to [1], new releases get decided on by the 'release manager', I'm >> not sure who's the current person to contact for that. > > Tom Stellard did the previous 3.4.2 release. I'm not sure if he plans > on doing any 3.5.x releases. >I am planning on doing 3.5.x releases. -Tom> It maybe a bit early to do a 3.5.1 release though. >
Tom Stellard
2014-Sep-10 16:12 UTC
[LLVMdev] Policy for applying fixes to released branches?
On 09/10/2014 11:57 AM, Reid Kleckner wrote:> We have one branch per point release, and we tag each micro release: > http://llvm.org/viewvc/llvm-project/llvm/branches/ > http://llvm.org/viewvc/llvm-project/llvm/tags/ > > 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. -Tom> In that case, merging to the 3.5 release branch is the correct procedure > to get it in 3.5.1.