> On May 29, 2016, at 5:16 AM, Zheng, Kai <kai.zh...@intel.com> wrote: > > Thanks Allen a lot. This is comprehensive. > >>> So if a patch has been committed to branch-2.8, branch-2, and trunk, then >>> the fix version should be 2.8.0 and only 2.8.0. > This sounds like the right rule I seem to need and want to know, but guess it > may change around the 3.0 release.
Not really. Patch committed to branch-2 and branch-3 and trunk? Then version should be whatever is sitting in branch-2. Fix version gets set to the lowest version, only. The only time that changes is when dealing with micro releases which will likely then need to have the micro and the minor listed (e.g., 2.8.1 and 2.9.0) since they are now effectively different release trains. This confusion is one of the reasons why having so many branches active is a bad thing, never mind the code stagnation problem. --------------------------------------------------------------------- To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-dev-h...@hadoop.apache.org
