I also join to previous question about new release.
It would be good to begin to prepare RC.
Can we make a plan for necessary functionality and bug fixes for further release?
On 2017-10-24 08:10, Ruslan Dautkhanov <[hidden email]> wrote:
> Sorry for bringing up an older topic .. I agree "latest" / "stable" makes a>
> lot of sense.>
> Also what was *not* discussed in this thread is release cadence target.>
> IMHO, 2-3 releases a year should give a quicker turnover to release latest>
> fixes and improvements / quicker feedback from the users?>
> Would be great to see 0.8.0 release soon..>
> I see on github there were a lot of awesome additions/commits since the>
> last release.>
> On Tue, Mar 21, 2017 at 10:57 AM, moon soo Lee <[hidden email]> wrote:>
> > Thanks for the opinion. Yes we can think about proper label. These are>
> > labels mentioned in this threads so far.>
> > 'Unstable', 'Stable', 'Old'>
> > 'Latest', 'Stable', 'Old'>
> > 'Beta', 'Stable', 'Old'>
> > Intention is not that we want to release 'unstable' version, i think.>
> > The intention is give user proper expectation that latest release may(and>
> > may not) include bug which we couldn't discovered in verification process>
> > like what happened in our previous release 0.7.0 and 0.6.0.>
> > These are h