Returning to this question: we’ve fixed 119 issues since we released 1.1.0 in February. I’d like to do an early April release of 1.2.0 so we can be done with the JSON.org <http://json.org/> license issue in plenty of time. Let’s plan to create a release candidate one week from today on 3/27. Thoughts?
I’m happy to volunteer for release manager unless someone else wants it. Anthony > On Feb 16, 2017, at 8:20 AM, Anthony Baker <aba...@pivotal.io> wrote: > > Great job everyone on releasing 1.1.0! Let’s get organized for the next > release :-) > > Scope: > We definitely need to focus on eliminating JSON.org prior to 4/31. See > GEODE-629, GEODE-2142, GEODE-2331, GEODE-2380. > Anything else? > > Timing: > I suggest shooting for a release candidate around mid-March if possible > (release often!) > > Release Manager: > Any volunteers? > > Note: as a process reminder please don’t set Fix Version in JIRA unless you > fix a bug that has been merged to develop or the issue has been prioritized > by the community for inclusion in a release. > > Thanks, > Anthony >
