Hi Justin, We will make sure that 3.1.x is not referred to as Apache release. The plan is to make the transition with creation of release-3.2 branch so that there is sufficient time to adopt Apache compatible practices. There are a number of source code changes (licensing related etc.) that will need to be completed.
Thanks, Thomas On Fri, Sep 25, 2015 at 9:05 AM, Justin Mclean <[email protected]> wrote: > Hi, > > > Thanks for pointing this out. There is no plan to release 3.1.1 in > Apache. > > Seems a little odd given the project is now part of the incubator, but as > long as it not referred to as an Apache release that would be OK. I assume > there are reasons for doing this, but would it be that hard to make it an > Apache release? > > > Do you foresee any issues just pushing the version changes and tags for > > 3.1.X to the ASF repo?] > > May cause a little confusion as you’ll have something that it tagged as a > release when it’s not a voted on Apache release. > > Thanks, > Justin
