The client-admin-api dependencies issue is already fixed in master. there's
one more PR pending for 2.8 which is to have interfaces and builders
instead of the POJOs exposed.

For (2), do you have the PR/commit?


--
Matteo Merli
<matteo.me...@gmail.com>


On Sat, Jun 5, 2021 at 12:31 PM Jerry Peng <jerry.boyang.p...@gmail.com>
wrote:

> Are the following issues fixed?
>
>    1. Pulsar-client-admin-api changes to not have dependencies (in
> progress)
>    2. Reverting external cluster URL External cluster URL
>    <
> https://github.com/apache/pulsar/blob/master/pulsar-common/src/main/java/org/apache/pulsar/common/functions/FunctionConfig.java#L100
> >
>
>
> If those issues are not fixed yet, the 2.8 release should wait until those
> issues are resolved as discussed in the Apache Pulsar community meetings.
>
> Best,
>
> Jerry
>
> On Sat, Jun 5, 2021 at 2:24 AM Guangning E <eguangn...@gmail.com> wrote:
>
> > +1
> >
> > Matteo Merli <mme...@apache.org> 于2021年6月5日周六 下午12:54写道:
> >
> > > +1
> > >
> > >
> > > --
> > > Matteo Merli
> > > <mme...@apache.org>
> > >
> > >
> > > On Fri, Jun 4, 2021 at 9:53 PM PengHui Li <peng...@apache.org> wrote:
> > >
> > > > Hi all,
> > > >
> > > > I have moved some PRs which are not merged yet but marked as
> milestone
> > > 2.8
> > > > to milestone 2.9, and add tags `release/2.7.3`, `release/2.8.1`.
> > > > All the moved PRs are not the blocker for the 2.8.0 release but all
> of
> > > them
> > > > are powerful features, great fixes, and enhancements.
> > > >
> > > > Here are the blockers of 2.8.0 release,
> > > >
> > > >
> > >
> >
> https://github.com/apache/pulsar/pulls?q=is%3Aopen+is%3Apr+milestone%3A2.8.0
> > > >
> > > > I will start to cut the 2.8.0 after all the blockers been resolved.
> Of
> > > > course, if PRs get merged before cutting the 2.8.0,
> > > > I will also contain them in 2.8.0 release.
> > > >
> > > > Please let me know if you have any questions about the 2.8.0 release.
> > > >
> > > > Regards,
> > > > Penghui
> > > >
> > > >
> > > >
> > > > Sijie Guo <guosi...@gmail.com> 于2021年5月18日周二 上午2:50写道:
> > > >
> > > > > 👍
> > > > >
> > > > > On Sun, May 16, 2021 at 11:11 PM Addison Higham <
> addis...@gmail.com>
> > > > > wrote:
> > > > >
> > > > > > Hi all,
> > > > > >
> > > > > > Really looking forward to this release and all the new
> > improvements.
> > > I
> > > > > > would be happy to volunteer as the release manager for this
> > release.
> > > > > >
> > > > > > Addison
> > > > > >
> > > > > > On Thu, May 13, 2021 at 8:37 PM Jia Zhai <zhai...@apache.org>
> > wrote:
> > > > > >
> > > > > > > +1
> > > > > > >
> > > > > > >
> > > > > > > On Wed, May 12, 2021 at 8:17 PM Anonymitaet _ <
> > > > > anonymita...@hotmail.com>
> > > > > > > wrote:
> > > > > > >
> > > > > > > > Hi all,
> > > > > > > >
> > > > > > > > Thanks for your great work on developing these wonderful
> > > features.
> > > > > > > >
> > > > > > > > Since documentation is one of the maturity indicators for
> > > measuring
> > > > > an
> > > > > > > > open-source project, for each release, technical writers try
> > > their
> > > > > best
> > > > > > > to
> > > > > > > > sync docs with code.
> > > > > > > >
> > > > > > > > To allow engineers and writers to work efficiently, may I
> > > suggest:
> > > > > > > >
> > > > > > > > - If your PR needs adding docs, feel free to add them
> > > accordingly.
> > > > > Then
> > > > > > > > you can ping technical writers (for example, me) to review.
> > > > > > > >
> > > > > > > > - If you find any PR or issue needs docs, do not hesitate to
> > add
> > > > them
> > > > > > or
> > > > > > > > label them with `doc-required`. This is an effective way to
> > help
> > > > > > > technical
> > > > > > > > writers know the gap and then fill it.
> > > > > > > >
> > > > > > > > Many thanks!
> > > > > > > >
> > > > > > > >     >
> > > > > > > >     > On Tue, May 11, 2021 at 1:38 AM PengHui Li <
> > > > peng...@apache.org
> > > > > >
> > > > > > > > wrote:
> > > > > > > >     >
> > > > > > > >     > > Hi, everyone
> > > > > > > >     > >
> > > > > > > >     > > I hope you’ve all been doing well. In June,  there
> are
> > 5
> > > > > months
> > > > > > > we
> > > > > > > >     > haven’t
> > > > > > > >     > > released a major version. So I would like to start an
> > > email
> > > > > > > thread
> > > > > > > > to
> > > > > > > >     > > discuss features that we planned for 2.8.0.
> > > > > > > >     > >
> > > > > > > >     > > There are some powerful features and enhancements in
> > > 2.8.0
> > > > > such
> > > > > > > as
> > > > > > > >     > >
> > > > > > > >     > > - Transactions
> > > > > > > >     > > - Exclusive Producer
> > > > > > > >     > > - Package management service
> > > > > > > >     > > - Client memory limit
> > > > > > > >     > > -  Pluggable metadata interface- Broker entry
> metadata
> > > > > > > >     > > - Streaming dispatcher
> > > > > > > >     > > - Get applied topic policy
> > > > > > > >     > > - Message Index of topic
> > > > > > > >     > >
> > > > > > > >     > > I just list some of them. And you can find all the
> > change
> > > > > lists
> > > > > > > > from
> > > > > > > >     > >
> > > https://github.com/apache/pulsar/pulls?q=milestone%3A2.8.0
> > > > > > > >     > > +-label%3Arelease%2F2.7.2+-label%3Arelease%2F2.7.1+
> > > > > > > >     > > <
> > > > > > > >     > >
> > > > > > > >     >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> https://github.com/apache/pulsar/pulls?q=milestone%3A2.7.0+-label%3Arelease%2F2.6.2+-label%3Arelease%2F2.6.1+
> > > > > > > >     > > >
> > > > > > > >     > > There
> > > > > > > >     > > are more than 800 commits.
> > > > > > > >     > >
> > > > > > > >     > > If you have any suggestions please let me know.
> > > > > > > >     > >
> > > > > > > >     > > I will organize a list for all major features in
> 2.8.0
> > > and
> > > > > will
> > > > > > > > update it
> > > > > > > >     > > in the email thread later.
> > > > > > > >     > >
> > > > > > > >     > > Regards,
> > > > > > > >     > > Penghui
> > > > > > > >     > >
> > > > > > > >     >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>

Reply via email to