Thanks Yusaku! On Wed, Oct 15, 2014 at 3:57 PM, Yusaku Sako <[email protected]> wrote:
> Hi Judes, > > https://issues.apache.org/jira/browse/AMBARI-6270 was already committed > and > marked 2.1.0 by mistake. > It has been marked fixVersion=2.0.0. > > https://issues.apache.org/jira/browse/AMBARI-6275 is a feature that may or > may not make it to 2.0.0 so it has been marked 2.1.0. > > Fix version has been removed from other JIRAs. > > Yusaku > > On Wed, Oct 15, 2014 at 1:48 PM, Judes Sarmiento <[email protected]> > wrote: > > > Hi, > > > > Quick question... > > > > I noticed that there are already 6 JIRAs with a Fix Version of 2.1. > > > > > > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20AMBARI%20AND%20fixVersion%20%3D%202.1.0 > > > > One of them already has a committed patch in trunk. > > > > Isn't everything that gets committed to trunk since the 1.7.0 branch got > > created supposed to have a Fix Version of 2.0.0? > > > > Is there a reason why we would want to have some JIRAs have a 2.1 Fix > > Version? > > > > Thanks, > > Judes > > > > -- > CONFIDENTIALITY NOTICE > NOTICE: This message is intended for the use of the individual or entity to > which it is addressed and may contain information that is confidential, > privileged and exempt from disclosure under applicable law. If the reader > of this message is not the intended recipient, you are hereby notified that > any printing, copying, dissemination, distribution, disclosure or > forwarding of this communication is strictly prohibited. If you have > received this communication in error, please contact the sender immediately > and delete it from your system. Thank You. >
