1) Proposal - we can rename the 2.0.0 version to 2.0.1-incubating as the next planned maintenance release (for now). All JIRAs targeted for 2.0.0 should be evaluated to see if any belong to the scope for the upcoming 2.0.0-incubating release or not.
2) Regarding comments on JIRA-875, I have created a new JIRA (HAWQ-895) for the investigation on migrating to semantic versioning. That raises the question, should version 2.0.0-incubating really be 2.0.0.0-incubating ? https://issues.apache.org/jira/browse/HAWQ-895 Thanks -Vineet On Tue, Jul 5, 2016 at 5:09 PM, Goden Yao <[email protected]> wrote: > Hi all, > > I want to raise some concerns around HAWQ versions we used in Apache JIRA. > We right now have: > > - 2.0.0-incubating (this is the upcoming release we're working on) > - 2.0.0 (this was used for JIRAs after originally planned > 2.0.0-incubating) , now I see a little bit issue if we releae > 2.0.0-incubating , what leaves with items associated with this version? > - 2.1.0 - supposedly , this is the next minor release > - 3.0.0 - supposedly, this is the next major release > - Backlog > > > Then I see this JIRA: https://issues.apache.org/jira/browse/HAWQ-875 > (*Upgrade > HAWQ version to 2.0.1.0*), which is not a version listed on the release > page. > Can we: > > - Clarify which version is for which release (goals, purpose, etc.) see > example I did for 2.0.0-incubating: > > https://cwiki.apache.org/confluence/display/HAWQ/HAWQ+Release+2.0.0-incubating > > - When you file JIRA, make sure you have a targeted version for it so > it's easy to track from release perspective. > > > Thanks > -Goden >
