I am going to prepare a release candidate from branch-0.3. Thanks everyone!
Tsz-Wo On Thu, Mar 28, 2019 at 7:23 PM Tsz Wo Sze <[email protected]> wrote: > > Rajeshbabu, > > Thanks a lot for the quick response! > > Tsz-Wo > > On Thu, Mar 28, 2019 at 7:06 PM [email protected] > <[email protected]> wrote: > > > > committed RATIS-510 to branch 0.3.0 Tsz. > > > > Thanks, > > Rajeshbabu. > > > > On Thu, Mar 28, 2019 at 4:28 PM [email protected] < > > [email protected]> wrote: > > > > > I will commit RATIS-510 Tez. > > > > > > Thanks, > > > Rajeshbabu. > > > > > > On Thu, Mar 28, 2019, 3:58 PM Tsz Wo Sze <[email protected] wrote: > > > > > >> All RATIS-503, RATIS-506 and RATIS-490 are now committed. However, we > > >> need RATIS-510 (missing Apache license header) or revert RATIS-475 > > >> from branch-0.3. > > >> > > >> Will see if we can roll a release tomorrow. > > >> > > >> Thanks. > > >> Tsz-Wo > > >> > > >> On Tue, Mar 26, 2019 at 12:09 AM Jitendra Pandey <[email protected]> > > >> wrote: > > >> > > > >> > +1 I would suggest we should cut a release candidate once following 3 > > >> are > > >> > included: > > >> > RATIS-503, RATIS-506 and RATIS-490, however RATIS-490 is not a blocker > > >> in > > >> > my opinion. > > >> > > > >> > On Mon, Mar 25, 2019 at 5:47 AM Tsz Wo Sze <[email protected]> wrote: > > >> > > > >> > > How about we roll a 0.3.0 release from branch-0.3? Please let me > > >> > > know > > >> > > if there are specific JIRAs we should include in 0.3.0. Thanks. > > >> > > > > >> > > Tsz-Wo > > >> > > > > >> > > > > >> > > > > >> > > > > >> > > On Fri, Mar 22, 2019 at 1:19 PM Tsz Wo Sze <[email protected]> > > >> wrote: > > >> > > > > > >> > > > I just have re-created branch-0.3. If you already have branch-0.3 > > >> > > > locally, "git pull" should be able to update all the changes. > > >> Thanks. > > >> > > > > > >> > > > Tsz-Wo > > >> > > > > > >> > > > On Thu, Mar 21, 2019 at 12:47 AM Mukul Kumar Singh > > >> > > > <[email protected]> wrote: > > >> > > > > > > >> > > > > +1, > > >> > > > > > > >> > > > > On 3/20/19, 9:20 PM, "Jitendra Pandey" <[email protected]> > > >> wrote: > > >> > > > > > > >> > > > > > I will merge everything in master to branch-0.3 (or > > >> re-create > > >> > > the 0.3 > > >> > > > > branch). > > >> > > > > > > >> > > > > +1 > > >> > > > > > > >> > > > > On Wed, Mar 20, 2019 at 7:58 AM Arpit Agarwal > > >> > > <[email protected]> > > >> > > > > wrote: > > >> > > > > > > >> > > > > > +1 for rebasing 0.3 to trunk. > > >> > > > > > > > >> > > > > > > > >> > > > > > > On Mar 20, 2019, at 2:37 AM, Tsz Wo Sze < > > >> [email protected]> > > >> > > wrote: > > >> > > > > > > > > >> > > > > > > If there is no objection, I will merge everything in > > >> master to > > >> > > > > > > branch-0.3 (or re-create the 0.3 branch) tomorrow. > > >> Thanks. > > >> > > > > > > > > >> > > > > > > Tsz-Wo > > >> > > > > > > > > >> > > > > > > On Fri, Mar 1, 2019 at 6:54 AM Jitendra Pandey < > > >> > > [email protected]> > > >> > > > > > wrote: > > >> > > > > > >> > > >> > > > > > >> +1 > > >> > > > > > >> There have been many fixes in trunk lately that need to > > >> be in > > >> > > 0.3 as > > >> > > > > > well. Therefore, it makes sense to rebase 0.3 to the > > >> > > > > current > > >> > > trunk. > > >> > > > > > >> > > >> > > > > > >> On 2/28/19, 2:49 PM, "Tsz Wo Sze" <[email protected]> > > >> wrote: > > >> > > > > > >> > > >> > > > > > >> Hi Marton, > > >> > > > > > >> > > >> > > > > > >> For Ozone, it probably needs trunk. How about we > > >> > > > > move > > >> > > everything in > > >> > > > > > >> trunk to 0.3? > > >> > > > > > >> > > >> > > > > > >> Tsz-Wo > > >> > > > > > >> > > >> > > > > > >> On Tue, Feb 26, 2019 at 6:59 AM Elek, Marton < > > >> > > [email protected]> > > >> > > > > > wrote: > > >> > > > > > >>> > > >> > > > > > >>> Hi, > > >> > > > > > >>> > > >> > > > > > >>> Any comment on this? > > >> > > > > > >>> > > >> > > > > > >>> What is the plan with the next release? > > >> > > > > > >>> > > >> > > > > > >>> Thanks, > > >> > > > > > >>> Marton > > >> > > > > > >>> > > >> > > > > > >>> On 2/6/19 11:21 AM, Elek, Marton wrote: > > >> > > > > > >>>> Bumping up this thread. > > >> > > > > > >>>> > > >> > > > > > >>>> I would like to use stable ratis release for the next > > >> ozone > > >> > > release. > > >> > > > > > >>>> > > >> > > > > > >>>> As I see branch-0.3 contains only RATIS-430. > > >> > > > > > >>>> > > >> > > > > > >>>> What is the current plan of releasing 0.3.0? > > >> > > > > > >>>> > > >> > > > > > >>>> Can we release branch-0.3 as is? > > >> > > > > > >>>> > > >> > > > > > >>>> Do we need to rebase branch-0.3 on top of the latest > > >> master? > > >> > > > > > >>>> > > >> > > > > > >>>> > > >> > > > > > >>>> Thanks, > > >> > > > > > >>>> Marton > > >> > > > > > >>>> > > >> > > > > > >>>> On 11/12/18 9:37 PM, Tsz Wo Sze wrote: > > >> > > > > > >>>>> Hi, > > >> > > > > > >>>>> > > >> > > > > > >>>>> We have around 80 commits after 0.2.0 release. How > > >> about > > >> > > we start > > >> > > > > > >>>>> preparing Ratis 0.3.0 release? > > >> > > > > > >>>>> > > >> > > > > > >>>>> We may create a 0.3.0 branch and change trunk to > > >> 0.4.0. > > >> > > Then, we can > > >> > > > > > >>>>> stabilize 0.3.0 before starting a vote. > > >> > > > > > >>>>> > > >> > > > > > >>>>> Tsz-Wo > > >> > > > > > >>>>> > > >> > > > > > >> > > >> > > > > > >> > > >> > > > > > >> > > >> > > > > > > > > >> > > > > > > > >> > > > > > > > >> > > > > > > >> > > > > > > >> > > > > >> > > >
