Jennifer - It might be worth starting separate threads for each of them to
drive the discussions.

Thanks,
Sijie

On Tue, Feb 2, 2021 at 11:59 PM Jinfeng Huang <h...@streamnative.io.invalid>
wrote:

> The following items are not discussed in this meeting due to time limits.
> If you have any idea on those items, feel free to discuss in the mailing
> list. Thank you.
>
>    - *Moving Pulsar 2.8 to JDK11*
>    - *EOS version*: since we introduce time-based release plan
>    <
> https://github.com/apache/pulsar/wiki/PIP-47%3A-Time-Based-Release-Plan>,
>    we'll have more and more Pulsar versions in the near future, and we're
>    maintaining all versions since 2.1(including incubating versions).
> Shall we
>    consider adopting a EOS strategy for Pulsar versions?
>    - *LTS* (long-term support of some version): When companies upgrading
>    Pulsar version, they will take risks and the cost of upgrading into
>    consideration. Shall we consider a long-term support for some Pulsar
>    versions, and apply security and necessary enhancements to this
> version? If
>    we have a LTS plan, companies using Pulsar will be guaranteed for a
> certain
>    period. Even if they do some customization, they know the structure and
>    core system will remain the same until some day.
>
>
> Best Regards,
> Jennifer
>
>
> On Wed, Feb 3, 2021 at 3:45 PM Jinfeng Huang <h...@streamnative.io> wrote:
>
> > It's great to start the Pulsar community meeting.
> > Thank you everybody for taking your time in this meeting, and thank Sijie
> > or coordinating.
> >
> > Best Regards,
> > Jennifer
> >
> >
> > On Wed, Feb 3, 2021 at 1:52 PM Jonathan Ellis <jbel...@gmail.com> wrote:
> >
> >> Great first meeting.  Thanks for coordinating, Sijie!
> >>
> >> On Tue, Feb 2, 2021 at 11:04 PM Sijie Guo <guosi...@gmail.com> wrote:
> >>
> >> > Thanks to everyone for participating in the meeting!
> >> >
> >> > The meeting notes are in
> >> >
> >> >
> >>
> https://docs.google.com/document/d/19dXkVXeU2q_nHmkG8zURjKnYlvD96TbKf5KjYyASsOE/edit#
> >> > .
> >> > The recording is also available at
> >> > https://github.com/apache/pulsar/wiki/Community-Meetings#recordings
> In
> >> > case
> >> > you didn't get a chance to attend the meeting.
> >> >
> >> > There are a couple of action items:
> >> >
> >> > 1. PIP-79: Reduce redundant produces: Matteo explained a few concerns.
> >> > These concerns will be shared back to the original PIP thread.
> >> > 2. PIP-78: Split the individual acks into multiple entries: Try to
> find
> >> a
> >> > solution to combine PIP-78 and the bitmap solution that Rajan
> proposed.
> >> > 3. PIP-45: @Rajan Dhabalia <rdhaba...@apache.org> and @Matteo Merli
> >> > <mme...@apache.org> to create a task list to track the progress of
> the
> >> > development of PIP-45.
> >> > 4. Docker image permission issues: Michael to take an action item to
> >> remove
> >> > "VOLUME" from the Dockerfile.
> >> >
> >> > As Matteo suggested, we will move the meeting on Thursday to start
> from
> >> > 8:30 AM. I will update the calendar.
> >> >
> >> > Thank you, everyone!
> >> >
> >> > - Sijie
> >> >
> >> > On Sat, Jan 30, 2021 at 11:01 AM Sijie Guo <guosi...@gmail.com>
> wrote:
> >> >
> >> > > Hi all,
> >> > >
> >> > > As discussed in the separate thread, the community will start the
> >> first
> >> > > community meeting next week. To address timezone issues, there are
> two
> >> > > meetings. Feel free to join the meetings that work for you. If you
> >> have
> >> > > anything to discuss, please add a line item to the agenda:
> >> > >
> >> >
> >>
> https://docs.google.com/document/d/19dXkVXeU2q_nHmkG8zURjKnYlvD96TbKf5KjYyASsOE/edit
> >> > >
> >> > > - 2/2 (Tuesday): 4 PM - 5 PM PST / 8 AM - 9 AM China Time
> >> > > - 2/4 (Thursday): 8 AM - 9 AM PST / 5 PM - 6 PM CET
> >> > >
> >> > > You can always find the meeting minutes & recordings on this wiki
> >> page:
> >> > > https://github.com/apache/pulsar/wiki/Community-Meetings
> >> > >
> >> > > Looking forward to the first meeting!
> >> > >
> >> > > - Sijie
> >> > >
> >> >
> >>
> >>
> >> --
> >> Jonathan Ellis
> >> co-founder, http://www.datastax.com
> >> @spyced
> >>
> >
>

Reply via email to