Looks like hive-on-tez and hive-on-spark didn't update the fix version after merge to trunk. But I think updating the fix version after merge makes sense.
On Thu, Feb 19, 2015 at 11:17 AM, Thejas Nair <thejas.n...@gmail.com> wrote: > I agree, using a label for fix version makes sense in this case. I believe > that is what had been done for hive-on-spark and hive-on-tez. > > > On Thu, Feb 19, 2015 at 10:56 AM, Alan Gates <alanfga...@gmail.com> wrote: > >> I've been marking JIRAs on this branch as fixed in 1.2, since that's the >> next version. But that seems wrong as I doubt this code will be in by >> 1.2. What's the usual practice here? It seems it would make sense to make >> a label for this branch and mark them as fixed with that label and then >> when we actually release this in a version we can update all the JIRAs with >> that label. >> >> Alan. >> > >
