On 12/12/13 2:06 pm, "sebgoa" <run...@gmail.com> wrote:
>>developers distributed across the globe I think it is very >> difficult to control the commits going into a branch after RC has been >> cut. As a RN I can only go thru the commits and see if any of those can >> cause unwanted changes and try to test those out. >>> >> > >Abhi, as RN I would support you if you wanted to revert commits made to >the branch until the release is out. >You can call for a code/commit freeze, with you as the only committer to >the branch. > I will request the committers not to make commit to 4.2.1, only if it is absolutely necessary. I am not sure what it will take to lock the branch but as Sebastien suggested I guess this is the time to lock down the branch till we have a 4.2.1 GA. -abhi >
