Thanks all. Encourage everyone to chime in more, so we can make a decision here!
On Thu, Apr 23, 2020 at 6:29 AM Sivabalan <[email protected]> wrote: > sounds good. We could go with a major by mid may. > > On Wed, Apr 22, 2020 at 12:58 PM Vinoth Chandar <[email protected]> wrote: > > > +1 on Sudha being the RM > > > > My preference would be to do a major release as well, targeting mid may > > (which means code freeze in 3 weeks?) > > This gives us enough time to land some major features as well as > stabilize > > them as much as possible. > > > > On Wed, Apr 22, 2020 at 3:21 AM Pratyaksh Sharma <[email protected]> > > wrote: > > > > > Major release looks good to me. > > > > > > On Wed, Apr 22, 2020 at 2:29 PM Bhavani Sudha <[email protected] > > > > > wrote: > > > > > > > Hello all, > > > > > > > > I wanted to kick start the discussion on timeline and logistics for > the > > > > next release. Here are couple things we need to figure out. > > > > > > > > 1. Should the next release be a minor or major release? > > > > 2. If its a minor release do we move the master back to 0.5.3 ( > > > > currently the master is at 0.6.0-SNAPSHOT). > > > > 3. Depending on minor or major release what is the timeline we > > should > > > > target? > > > > > > > > Here is my opinion: > > > > In addition to bug fixes, we have major features ( bootstrap, new > > indexes > > > > and bulk insert mode ) - either ready or almost ready. Hence, I > propose > > > we > > > > go with a major release. Assuming its a major release, may be mid of > > May > > > > might be a good timeline? > > > > > > > > > > > > I can volunteer to be the release manager if the community is okay > with > > > it. > > > > Please share your thoughts. > > > > > > > > Thanks, > > > > Sudha > > > > > > > > > > > > -- > Regards, > -Sivabalan >
