On 08/26/2011 11:38 AM, Steven Dake wrote:
On 08/25/2011 11:08 AM, Russell Bryant wrote:
> There are a few different models that we could follow for maintaining
> the release branch. I propose that committers share the responsibility
> of maintaining the branch. If the commit you are making is a bug fix,
> push it into release-0.4 and then "git cherry-pick -x" it to master.
> Otherwise, just push your changes to the branch they are applicable for
> as usual.
>
This proposal makes good sense, but it has been my experience in other
projects that if 1 person is not responsible for ensuring patches get
backported, patches don't get backported.
Worth a shot tho :)
Well I will review things. I'm actually not proposing backports,
though. I'm proposing that it be policy that if you're merging a bug
fix that is applicable to the release, that it gets committed there
first and then pulled over to master. I'm expecting committers to
understand and adhere to that policy so that we share the burden. It
has worked fine for me in my last major project.
--
Russell Bryant