The binding votes should be:
- David Jensen
- Daniel Blankensteiner
- Lari Hotar
I didn't vote on this release :D
I may omit most emails from this list since I moved my major focus to other
projects these days. But I'm glad to help review DotPulsar's RC. If you want to
notify me, you can keep
+1 (binding)
+ Signature and checksum match
+ Download link valid
+ Can compile from source
+ LICENSE and NOTICE present
On 2023/11/20 13:13:20 tison wrote:
> Hi everyone,
>
> Please review and vote on the release candidate #1 for the version 3.1.0,
> as follows:
>
> [ ] +1, Approve the release
+1 binding
- Checksum and signature matches.
- LICENSE and NOTICE are good.
- `gradle build` passed with JDK 17.
On 2023/11/17 19:12:28 Nicolò Boschi wrote:
> +1 binding
>
> I followed the instructions from here -
> https://github.com/apache/pulsar-client-reactive
> /wiki/Release-process#release
+1 binding
Thanks for your proposal.
On 2023/11/15 03:39:42 Pengcheng Jiang wrote:
> Hi Pulsar Community,
>
> This thread is to start a vote for PIP-312: Use StateStoreProvider to
> manage state in Pulsar Functions endpoints.
>
> I start the voting process since there are some approves for the
PIP-305 has passed with 3 +1 binding votes and 1 +1 non-binding vote.
3 +1 bindings vote
* tison
* Jiwei Guo
* PengHui Li
1 +1 non-binding vote
Zixuan Liu
On 2023/10/17 07:23:29 Diego Salvi wrote:
> Hi Community,
>
> This thread is to start a vote for PIP-305.
>
> PIP: https://github.com/apac
+1 binding
On 2023/10/17 07:23:29 Diego Salvi wrote:
> Hi Community,
>
> This thread is to start a vote for PIP-305.
>
> PIP: https://github.com/apache/pulsar/pull/21352
> Discussion thread:
> https://lists.apache.org/thread/p0870y7o6brv5y1ghn5tz9hvs24bl1k4
>
> Best regards
> Diego Salvi
>
+1 Thank you!
On 2023/10/12 15:00:35 Diego Salvi wrote:
> Hi Pulsar Community,
>
> This is a PIP discussion on how support custom DNSes configuration to be
> used by the Pulsar Client.
>
> This is the PIP issue https://github.com/apache/pulsar/pull/21352
>
> # Motivation
>
> Currently Pulsar c
Hi David,
Glad to see you participating in the vote process.
Generally, on a vote for release candidate, we +1 with reasons. You can take
Zike's reply as an example.
On 2023/09/06 17:29:10 David Jensen wrote:
> Thanks for helping to bring this release forward, Tison :)
>
> +1 (non-binding)
>
+1 (binding)
Thanks for driving the proposal!
On 2023/08/25 06:52:38 Xiangying Meng wrote:
> Hi Pulsar Community,
>
> This is the vote thread for PIP 296:
> https://github.com/apache/pulsar/pull/21052
>
> This PIP will help to improve the flexibility of Reader usage.
>
> Thanks,
> Xiangying
>
+1 (non-binding)
On 2023/07/07 09:25:22 Joo Hyuk Kim wrote:
> Hi community,
>
> This PIP has received a couple of approvals in github PR link [1]
> So I thought it's time to vote.
>
> ## Motivation
>
> In the current Pulsar codebase, the logic to parse CLI arguments for
> measurement units like
FYI - the proposal is applied https://issues.apache.org/jira/browse/INFRA-24636.
On 2023/06/02 02:25:55 Dave Fisher wrote:
> I think that INFRA would accept a DISCUSSION that looks for LAZY CONSENSUS.
>
> Sent from my iPhone
>
> > On Jun 1, 2023, at 7:18 PM, tison wrote:
> >
> > While we can
Filed a ticket at https://issues.apache.org/jira/browse/INFRA-24567
On 2023/05/07 14:20:58 Dave Fisher wrote:
> Hi -
>
> +1 to this. And yes all that’s needed is an INFRA JIRA with a link to this
> thread.
>
> Best,
> Dave
>
> Sent from my iPhone
>
> > On May 7, 2023, at 3:35 AM, tison wrote
Hi Baodi,
When running the tls test you provided, I encountered this error:
$ node tls-oauth2.js
[INFO][ClientConnection:190] [ ->
pulsar+ssl://baodi-test-7407d844-b456-49e1-987c-24f1a5c162cb.usce1-whale.test.g.sn2.dev:6651]
Create ClientConnection, timeout=1
[INFO][ConnectionPool:97] Crea
So here is the ticket: https://issues.apache.org/jira/browse/INFRA-24010
On 2022/12/16 00:55:39 Matteo Merli wrote:
> Yes, it was my mistake. I couldn't find a way to do it in Gitbox
> though. :/ Probably it does require an INFRA ticket.
> --
> Matteo Merli
>
>
> On Thu, Dec 15, 2022 at 3:58 PM
In the Kvrocks community, we meet the same problem and redirect the mails to
issues@[1].
Although, three points here:
1. Follow the ASF policy all effective discussions should happen on the mailing
list, while to issues@ should be also "on the list".
2. For personal mailbox, you can set up a fi
One thing I'd like to make clear: this is a temporary solution, and we'll
re-enable branch protection after the actions are performed (or relax to 2.9.4
released).
If it's the case, please file an issue and assign yourself to revert on time :)
On 2022/11/25 04:28:45 丛搏 wrote:
> Hi, pulsar commu
16 matches
Mail list logo
