Nudge, any thoughts?
On Sun, Dec 29, 2013 at 1:25 AM, Raymie Stata <rst...@altiscale.com> wrote: > In discussing YARN-1295 it's become clear that I'm confused about the > outcome of the "Next releases" thread. I had assumed there would be > patch releases to 2.2, and indeed one would be coming out early Q1. > Is this correct? > > If so, then things seem a little messed-up right now in 2.2-land. > There already is a branch-2.2.1, but there hasn't been a release. And > branch-2.2 has Maven version 2.2.2-SNAPSHOT. Due to the "2.3 rename" > a few weeks ago, it might be that the first patch release for 2.2 > needs to be 2.2.2. But if so, notice these lists of fixes for 2.2.1: > > https://issues.apache.org/jira/browse/YARN/fixforversion/12325667 > https://issues.apache.org/jira/browse/HDFS/fixforversion/12325666 > > Do these need to have their fix-versions updated? > > Raymie > > > P.S. While we're on the subject of point releases, let me check my > assumptions. > > I assumed that, for release x.y.z, fixes deemed to be "critical bug > fixes" would be put into branch-x.y as a matter of course. The Maven > release-number in branch-x.y would be x.y.(z+1)-SNAPSHOT, and JIRAs > (to be) committed to branch-x.y would have x.y.(z+1) as one of their > fix-versions. > > When enough fixes have accumulated to warrant a release, or when a fix > comes up that is critical enough to warrant an immediate release, then > branch-x-y is branched to branch-x.y.(z+1), and a release is made. > > (As Hadoop itself moves from x.y to x.(y+1) and then x.(y+2), the > threshold for what is considered to be a "critical bug" would > naturally start to rise, as the effort of back-porting goes up.) > > Do I have it right?
