Good catch!
I'll trigger a new RC.
For the future we need to have a procedure to not allow this kind of issues.
Maybe we should remove "release/blocker" labels once they are merged
into the release branch and ensure there are 0 "release/blocker"
before cutting the release ?
Le jeu. 27 avr. 2023 à
Yes, it should be documented how we should use the "release/blocker" label.
1. Add this label for the PR that should be included in the release candidate.
2. After it's merged, cherry-pick it into the release branch and
remove the label.
3. Ensure this label does not exist when starting a vote.
Th
Hi,
I am noticing that the users@pulsar.a.o is turning into a ANNOUNCEMENT
list, and not really an active forum to helpful users. Is there some
other forum where this help is happening, or is this community only
consisting of the developers of the product?
Cheers
Niclas
Original M
Hi Niclas,
I think https://github.com/apache/pulsar/discussions/categories/q-a is the
correct place. Or you can find more contact info at
https://pulsar.apache.org/community/#section-discussions.
Best,
tison.
Niclas Hedhman 于2023年4月27日周四 16:59写道：
> Hi,
>
> I am noticing that the users@pulsar.
This is the fourth release candidate for Apache Pulsar, version 3.0.0.
It fixes the following issues:
https://github.com/apache/pulsar/milestone/34?closed=1
*** Please download, test and vote on this release. This vote will
stay open for at least 72 hours ***
Note that we are voting upon the sou
Hi all,
I'm very excited to release a PIP I've been working on in the past 11
months, which I think will be immensely valuable to Pulsar, which I like so
much.
PIP: https://github.com/apache/pulsar/issues/20197
I'm quoting here the preface:
=== QUOTE START ===
Roughly 11 months ago, I started
Hi All,
Based on [1], Pulsar has various primitive schema types and has a very
clear mapping between java classes to primitive schema types.
But in code [2], Pulsar Function Source only handles the byte and String
java classes primitive schema mapping while default all other primitive
types to JS
Hi, All
I've got two questions want to discuss with you guys.
1. I am wondering if we should draft PIP for small metrics changes, e.g:
https://github.com/apache/pulsar/pull/20147
2. We haven't declear we should draft a PIP for configuration changes. why?
Refer to: https://github.com/apache/pu
Hi,
Thank you Mattison for starting this thread because I am feeling some of
the community members are making new contributors' life difficult and
trying to enforce rules which were never discussed and discourage them from
contributing to Pulsar. I really don't want to see the Pulsar community
bec
Totally agree. I have seen some patches with little change worth to do, but
stopped making progress, only being told an pip is needed.
I think if we have one fast-path for notice small changes like metrics or
configuration.
some pip to add configuration is also simple enough. like just add an
The problem is not related to whether the patch is simple. It is,
adding configurations were very casual in the past few years. Let's
look at how many configurations we have from a discussion [1] I
started a few months ago.
Adding a configuration is simple, removing it is hard.
Most of these conf
Hello Neng,
IMO, we should update code[2] to follow the doc, and for existing
functions, if they are in running status, they won't touch code[2]; and for
a new run, functions
will fail to start, and this will remind users to update their function
Regards,
Pengcheng Jiang
Neng Lu 于2023年4月28日周五 0
12 matches
Mail list logo
