2.0.x never made it to a release and should not be released 2.1.0 is what we are bug fixing in, preparing for release 2.1.1 is what we are working on in master 2.1.2 is for future planning
1.0.3 is also for future on the 1.x line, but we will likely not do this release in favor of all work being on >=2.1.x. If there are major issues with 1.x we would cut a 1.0.3 release. We need to publish an updated development flow. We will be: - actively developing in master - when we approach a release we will merge master into release - as we do release testing we will put bug fixes in release - once we cut an Apache release we will branch and have a release version as the name. We will also merge release back into master at this time. This will make it easier and cleaner. Also, versions were rarely used in JIRA in the past and half the tickets are duplicated in more than one JIRA project outside Apache. It was not well maintained or groomed. We hope to change this in the future and be more diligent. -------------------------------------------------------------- Jeff West | Engineering | apigee <http://apigee.com/> | m: +1.214.450.9378 | twitter <https://twitter.com/jeffreyawest>@ <http://twitter.com/USERNAME>j <http://twitter.com/USERNAME>effreyawest @apigee <https://twitter.com/apigee> | Skype jeffrey.a.west > On Jan 26, 2016, at 3:36 PM, lewis john mcgibbney <[email protected]> wrote: > > Hi dev@, > I am puzzled as to what the Roadmap looks like for Usergrid > > https://issues.apache.org/jira/browse/USERGRID/?selectedTab=com.atlassian.jira.jira-projects-plugin:roadmap-panel > > It seems literally all over the place, with issues being addressed and > resolved for branches which are not even available in Git! > > Can anyone shine some light on to what new issues should be resolved > against? > Thanks > Lewis
