In one of the previous community syncs, we decided to try time based releases (roughly a month apart) going forward since 1) we have enough meaty stuff landing every month and 2) gives users a cadence of releases.
While 0.23.0 vote is still in progress, the first RC was cut July 3rd, so cutting an RC for 24.0 early august follows the cadence. Regarding stable even releases, I personally don't like that idea. I would like every release to be stable and well tested. That is one of the reasons we are giving a longer vote time for RCs. Thanks On Tue, Jul 21, 2015 at 11:24 AM, haosdent <haosd...@gmail.com> wrote: > Or odd number version is no stable version while the even number version is > a stable version, just like HBase. > > On Wed, Jul 22, 2015 at 2:22 AM, haosdent <haosd...@gmail.com> wrote: > > > Is it too fast to release 0.24, because 0.23 is still rc3 now. > > > > On Wed, Jul 22, 2015 at 2:02 AM, Vinod Kone <vinodk...@gmail.com> wrote: > > > >> Hi folks, > >> > >> I will be the release manager for the upcoming release (ETA early > August). > >> > >> To prep for the release (and make my life easy) I'm planning to remove > the > >> target versions for all *unresolved* tickets that have a target version > >> 0.24.0. > >> > >> I would like folks to explicitly set the target version to 0.24.0* for > >> tickets they want to absolutely land in the next release (keeping in > mind > >> the time frame). If you are unsure, please reach out to me or reply to > >> this > >> thread. > >> > >> The main blocking feature for this release is going to the new HTTP API. > >> > >> Thanks, > >> Vinod > >> > >> P.S. If things go according to plan we might make this 1.0 release! > >> > > > > > > > > -- > > Best Regards, > > Haosdent Huang > > > > > > -- > Best Regards, > Haosdent Huang >
