Release 4.7.0

[Sijie Guo <gu...@gmail.com>]

Hi all,

We have about one month to cut release 4.7.0. Please go through the issues
you filed, if you would like them to be included in 4.7.0, please label
them as `4.7.0`. I would cut the release branch and freeze the features
that will be included in 4.7.0 in a week or so.

- Sijie

Re: Release 4.7.0

[Jia Zhai <zh...@gmail.com>]

👍

On Mon, Mar 12, 2018 at 3:19 PM, Enrico Olivelli <eo...@gmail.com>
wrote:

> Il lun 12 mar 2018, 07:50 Sijie Guo <gu...@gmail.com> ha scritto:
>
> > Updates on release 4.7:
> >
> > Since Pulsar is switching from using yahoo release to apache release, I
> am
> > delaying release 4.7.0 for about one month, so we have enough time to
> test
> > Pulsar to make sure yahoo changes are ported correctly back in 4.7.
> Expect
> > to cut a release branch in 2 weeks and be able to release by end of
> March.
> >
> > At the same time, I would like to include following BPs since they are
> > either completed or half-way through them.
> >
> > - BP-27: New BookKeeper CLI
> >    - Migrate the commands in BookieShell
> > - BP-29: Metadata Service URI
> > - BP-26: DLog (website/documentation update)
> >
> >
> > Also, I might be a bit busy on March. Jia will help me with some of the
> > tasks and do the actual release work.
> >
>
>
> I agree on this plan.
> Enrico
>
>
>
> > - Sijie
> >
> >
> > On Wed, Jan 31, 2018 at 10:52 PM, Sijie Guo <gu...@gmail.com> wrote:
> >
> > > Hi all,
> > >
> > > We have about one month to cut release 4.7.0. Please go through the
> > issues
> > > you filed, if you would like them to be included in 4.7.0, please label
> > > them as `4.7.0`. I would cut the release branch and freeze the features
> > > that will be included in 4.7.0 in a week or so.
> > >
> > > - Sijie
> > >
> >
> --
>
>
> -- Enrico Olivelli
>

Re: Release 4.7.0

[Enrico Olivelli <eo...@gmail.com>]

Il lun 12 mar 2018, 07:50 Sijie Guo <gu...@gmail.com> ha scritto:

> Updates on release 4.7:
>
> Since Pulsar is switching from using yahoo release to apache release, I am
> delaying release 4.7.0 for about one month, so we have enough time to test
> Pulsar to make sure yahoo changes are ported correctly back in 4.7. Expect
> to cut a release branch in 2 weeks and be able to release by end of March.
>
> At the same time, I would like to include following BPs since they are
> either completed or half-way through them.
>
> - BP-27: New BookKeeper CLI
>    - Migrate the commands in BookieShell
> - BP-29: Metadata Service URI
> - BP-26: DLog (website/documentation update)
>
>
> Also, I might be a bit busy on March. Jia will help me with some of the
> tasks and do the actual release work.
>


I agree on this plan.
Enrico



> - Sijie
>
>
> On Wed, Jan 31, 2018 at 10:52 PM, Sijie Guo <gu...@gmail.com> wrote:
>
> > Hi all,
> >
> > We have about one month to cut release 4.7.0. Please go through the
> issues
> > you filed, if you would like them to be included in 4.7.0, please label
> > them as `4.7.0`. I would cut the release branch and freeze the features
> > that will be included in 4.7.0 in a week or so.
> >
> > - Sijie
> >
>
-- 


-- Enrico Olivelli

Re: Release 4.7.0

[Sijie Guo <gu...@gmail.com>]

Updates on release 4.7:

Since Pulsar is switching from using yahoo release to apache release, I am
delaying release 4.7.0 for about one month, so we have enough time to test
Pulsar to make sure yahoo changes are ported correctly back in 4.7. Expect
to cut a release branch in 2 weeks and be able to release by end of March.

At the same time, I would like to include following BPs since they are
either completed or half-way through them.

- BP-27: New BookKeeper CLI
   - Migrate the commands in BookieShell
- BP-29: Metadata Service URI
- BP-26: DLog (website/documentation update)


Also, I might be a bit busy on March. Jia will help me with some of the
tasks and do the actual release work.

- Sijie


On Wed, Jan 31, 2018 at 10:52 PM, Sijie Guo <gu...@gmail.com> wrote:

> Hi all,
>
> We have about one month to cut release 4.7.0. Please go through the issues
> you filed, if you would like them to be included in 4.7.0, please label
> them as `4.7.0`. I would cut the release branch and freeze the features
> that will be included in 4.7.0 in a week or so.
>
> - Sijie
>

Re: Release 4.7.0

[Sijie Guo <gu...@gmail.com>]

On Thu, Feb 1, 2018 at 2:52 AM, Ivan Kelly <iv...@apache.org> wrote:

> > We have about one month to cut release 4.7.0. Please go through the
> issues
> > you filed, if you would like them to be included in 4.7.0, please label
> > them as `4.7.0`. I would cut the release branch and freeze the features
> > that will be included in 4.7.0 in a week or so.
>
> I've gone though all created by me, bumped some to 4.8.0, ping people
> on others (all jira migrated as marked as created by me).
>
> Is the status of the new apis going to change this release?
>

Don't think so. Before we can change the status, we at least need to move
all the test cases to use new api. After all bookkeeper code base is moved
to use the new API, we can then change it from "Unstable" to "Evolving".
I would expect it takes one more release after that, before we can change
it from "Evolve" to "Stable".

However I don't think there are efforts on pushing this, since we have
other higher priority tasks to address.


>
> -Ivan
>

Re: Release 4.7.0

[Ivan Kelly <iv...@apache.org>]

> We have about one month to cut release 4.7.0. Please go through the issues
> you filed, if you would like them to be included in 4.7.0, please label
> them as `4.7.0`. I would cut the release branch and freeze the features
> that will be included in 4.7.0 in a week or so.

I've gone though all created by me, bumped some to 4.8.0, ping people
on others (all jira migrated as marked as created by me).

Is the status of the new apis going to change this release?

-Ivan