On Mon, Jul 27, 2015 at 1:03 PM, Dmitriy Setrakyan <[email protected]> wrote:
> On Mon, Jul 27, 2015 at 12:26 AM, Branko Čibej <[email protected]> wrote: > > > > Can you describe at which point a master becomes a release branch in > > > Subversion? > > > > http://subversion.apache.org/docs/community-guide/releasing.html > > > > > Also, what happens if an occasional bad commit sneaked into the release > > branch? > > > > It's almost impossible for that to happen, as per the process described > > on that page. But if it does, we just revert it and try again, usually > > after creating or fixing a backport branch. > > > > I kind of see the point of bypassing reviews on simple fixes. However, > *simple* is a relative term. I think we should define what *simple* means. > I have some ideas, but I would like to hear some other opinions as well. > > For me, simple is anything which is obvious to larger part of community. A complex bug fix or a feature is not simple, but using the correct Collection method (or the more efficient one) is. Thoughts?
