> I agree, in that case we'd have to release a 5.2.1, otherwise the users will > go somewhere else. > > I assume whoever was release manager for the 5.2.0 release would own the > subsequent maintenance releases -- including deciding whether or not there is > one, and what goes in if there is one. I'm unclear on who would be expected > to merge a given fix from master into the 5.2.x branch. Perhaps the release > manager should create a ticket then assign it to whoever committed the > original patch? So by committing a patch you agree to subsequently merge it > into other branches if asked to do so by a release manager in the project. > > -kevin
I think that is up to us to define. (and iterate if it we find it doesn't work) --David
