[GitHub] [pulsar-site] urfreespace merged pull request #15: feat: new releases notes page

[GitBox]

urfreespace merged pull request #15:
URL: https://github.com/apache/pulsar-site/pull/15


   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@pulsar.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[VOTE][PIP-146] ManagedCursorInfo compression

[Zixuan Liu]

Hi Pulsar community,

I want to start this PIP - https://github.com/apache/pulsar/issues/14529

Thanks,
Zixuan

Re: [VOTE][PIP-146] ManagedCursorInfo compression

[Zixuan Liu]

Discussion thread:
https://lists.apache.org/thread/j92bzsby9n2ozc9gcw5psgcy2026l1wm

Zixuan Liu  于2022年3月9日周三 17:18写道：

> Hi Pulsar community,
>
> I want to start this PIP - https://github.com/apache/pulsar/issues/14529
>
> Thanks,
> Zixuan
>
>

Re: [VOTE] [PIP-144] Making SchemaRegistry implementation configurable

[Enrico Olivelli]

+1 (binding)

Enrico

Il giorno mer 9 mar 2022 alle ore 06:39 Aparajita Singh
 ha scritto:
>
> Hi,
>
> I would like to start a vote for PIP-144:
> https://github.com/apache/pulsar/issues/14395
> Discussion thread:
> https://lists.apache.org/thread/z97cvs8mvhlydv8rbnqk4d0c7mp8rwt3
>
> --
> Thanks,
> Aparajita

[GitHub] [pulsar-client-node] nkurihar commented on issue #201: Support for Dead Letter Topics in Consumers?

[GitBox]

nkurihar commented on issue #201:
URL: 
https://github.com/apache/pulsar-client-node/issues/201#issuecomment-1062724990


   >  Is there a timeline on when this would be added, if it exists?
   
   No, unfortunately we have not decided the timeline to add this feature yet...


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@pulsar.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [pulsar-site] Anonymitaet commented on pull request #8: Integrating changes from community feedback

[GitBox]

Anonymitaet commented on pull request #8:
URL: https://github.com/apache/pulsar-site/pull/8#issuecomment-1062845878


   @Paul-TT could u pls resolve conflicts？


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@pulsar.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Re: [Discuss] Create Pulsar client release notes

[Yu]

Hi Michael,

Thanks for your suggestions!



#1

> I am happy to submit the PR to move this information from the "Versioning
Policy" page to the downloads page. Which doc's do I need to update in
order to move this table? (This relates to my other thread asking about
where to put this information, and because of the in-flight website
changes, I am confused about where to contribute this update.)

I think the content of the "Versioning policy" chapter [1] should be split
into different places:

> The Pulsar project adheres to Semantic Versioning. Existing releases can
expect patches for bugs and security vulnerabilities. New features will
target minor releases.

This part belongs to "semantic versioning", which should go to the "Release
plan" sub-page mentioned in #2.

> When upgrading an existing cluster, it is important to upgrade components
linearly through each minor version. For example, when upgrading from 2.8.x
to 2.10.x, it is important to upgrade to 2.9.x before going to 2.10.x.

This part can go to the Download page. You can modify this file [2].


#2

> I think that the versioning policy and the time based release plan could
be too long for the downloads page. I propose that we have a dedicated page
for this information and link to that page from the downloads page.

+1.
How about adding a "Release plan" sub-page under the "Release notes" page?
The "Release plan" page explains everything about the Pulsar release, such
as release frequency, semantic versioning, maintenance life cycle, and
other content in PIP 47, etc.

I highlight the changes in yellow, PTAL [3].

And here is a preview (just DRAFT) of the new "Release notes" page. [4]



#3

> Further, I think we should move unsupported versions to another downloads
page to make it even more obvious what is currently supported.

Instead of creating another download page, we can readjust the current
download page, such as adding notes / creating tables / other formats to
separate "unsupported versions" and "supported versions" and make the info
more prominent.



#4

> Recently, we got some negative feedback from users.

They are some users' feedback from Slack. We've replied to them and keep
them updated once we make progress on the PIP 148.



[1]
https://pulsar.apache.org/docs/en/next/security-policy-and-supported-versions/#versioning-policy
[2]
https://github.com/apache/pulsar/blob/master/site2/website/pages/en/download.js
[3]
https://docs.google.com/spreadsheets/d/1MT8vt0620Cy4tggKk3gDVPbnhH7GVakld-5aDYCGAko/edit#gid=1749306691

[4] https://pulsar-next.staged.apache.org/releases-notes/




On Wed, Mar 9, 2022 at 7:17 AM Michael Marshall 
wrote:

> > Add necessary explanations, such as time-based release plan, release
> frequency, semantic versioning, maintenance life cycle, etc.
>
> I support adding the release dates and support dates to the downloads
> page. This makes it clear which downloads are supported and for how
> long. I am happy to submit the PR to move this information from the
> "Versioning Policy" page to the downloads page. Which doc's do I need
> to update in order to move this table? (This relates to my other thread
> asking about where to put this information, and because of the in-flight
> website changes, I am confused about where to contribute this update.)
>
> Further, I think we should move unsupported versions to another
> downloads page to make it even more obvious what is currently
> supported.
>
> In reviewing the PIP 148 sheet, I think that the versioning policy and
> the time based release plan could be too long for the downloads page.
> I propose that we have a dedicated page for this information and link
> to that page from the downloads page. I have actually been planning to
> contribute a "Release Plan" page to our website, so if you direct me
> where I should add it, I can convert PIP 47 into a page on the
> website. (Note that PIP 47 needs to be modified and should not be
> directly translated to the website, which is why I would like to drive
> the effort to get it onto our website. I will start a separate thread
> on the ML to discuss our release process moving forward once I know
> where to put this page on the website.)
>
> > Recently, we got some negative feedback from users.
>
> Are you able to provide a reference to the source of this feedback?
>
> Thanks!
> Michael
>
> On Mon, Mar 7, 2022 at 10:18 PM Yu  wrote:
> >
> > Thanks Li Li, for always helping in making breaking changes to Pulsar!
> >
> > On Tue, Mar 8, 2022 at 11:01 AM Li Li  wrote:
> >
> > > +1, I will do this task.
> > >
> > > Li Li
> > >
> > > > On Mar 8, 2022, at 8:39 AM, Huanli Meng  .INVALID>
> > > wrote:
> > > >
> > > > +1
> > > >
> > > > BR//Huanli
> > > >
> > > >> On Mar 8, 2022, at 3:52 AM, Sijie Guo  wrote:
> > > >>
> > > >> Yu, thank you for driving this effort! Great to see a proposal
> focusing
> > > on this! +1
> > > >>
> > > >> O

Re: [VOTE][PIP-146] ManagedCursorInfo compression

[PengHui Li]

+1

Penghui

On Wed, Mar 9, 2022 at 5:21 PM Zixuan Liu  wrote:

> Discussion thread:
> https://lists.apache.org/thread/j92bzsby9n2ozc9gcw5psgcy2026l1wm
>
> Zixuan Liu  于2022年3月9日周三 17:18写道：
>
> > Hi Pulsar community,
> >
> > I want to start this PIP - https://github.com/apache/pulsar/issues/14529
> >
> > Thanks,
> > Zixuan
> >
> >
>

Re: [VOTE] [PIP-144] Making SchemaRegistry implementation configurable

[PengHui Li]

+1

Penghui

On Wed, Mar 9, 2022 at 5:27 PM Enrico Olivelli  wrote:

> +1 (binding)
>
> Enrico
>
> Il giorno mer 9 mar 2022 alle ore 06:39 Aparajita Singh
>  ha scritto:
> >
> > Hi,
> >
> > I would like to start a vote for PIP-144:
> > https://github.com/apache/pulsar/issues/14395
> > Discussion thread:
> > https://lists.apache.org/thread/z97cvs8mvhlydv8rbnqk4d0c7mp8rwt3
> >
> > --
> > Thanks,
> > Aparajita
>

Re: [DISUSS] Improve unit test stability

[Lari Hotari]

Good question. I agree that we should strive to fix flaky tests as top priority.

For more background, please read the document that was compiled about a year 
ago:
https://docs.google.com/document/d/10lmn4pW1IsT_8D1ZE0vMjASX0HhjdGdjB794iyScwns/edit

and these mailing list discussions:
https://lists.apache.org/thread/6ntz6gfmksonp901hhs7plf4yzok2qk1
https://lists.apache.org/thread/47j2l9n9q2d5fdrjvnfjr471b35lh8dk

To coordinating the flaky test fixing, I have been creating reports of the most 
flaky tests and posting the report to the mailing list every 1-2 months. The 
latest reporting email:
https://lists.apache.org/thread/25wf94k2gqxlb0rn7rrtsh03h7z6zlj0
Thanks to the active contributors, a lot of the most flaky tests have already 
been fixed after the report was created. There has been a lot of good progress 
in the last year.

I'd be happy to hear how we could improve our ways of working to address the 
flaky tests asap. More contributors and improvements ideas are very welcome! 

When you encounter a flaky test, please report it and fix it:
1) please search for an existing issues or search for all flaky issues with
"flaky" or the test class name (without package) in the search:
https://github.com/apache/pulsar/issues?q=is%3Aopen+flaky+sort%3Aupdated-desc

2) If there isn't an issue for a particular flaky test failure that you'd
like to fix, please create an issue using the "Flaky test" template at
https://github.com/apache/pulsar/issues/new/choose

3) Please comment on the issue that you are working on it.

Please join the #testing channel on Slack if you'd like to ask questions and 
share tips about
reproducing flaky tests locally and how to fix them. There's more work to be 
done in reducing flakiness. I'm looking forward to more contributors joining 
the efforts! Welcome!

-Lari

On 2022/03/09 01:47:40 Baozi wrote:
> Thank your reply. I agree with the idea mentioned above.
> 
> 
> However, I have a question: Why don't we fix all the flaky tests first? 
> After,  We can not allow all tests to retry. 
> 1. Fix all existing flaky tests.
> 2. Then, in each PR, for all tests, as long as they fail, let the job fail
> 3. If there are new or modified tests in this PR, it needs to be run N times
> 
> In this way, we can try our best to ensure that the tests in our master 
> branch are always stable.
> 
> 
> > 2022年3月9日 08:3306，PengHui Li  写道：
> > 
> >> Alternatively, would it be possible to only retry tests that are
> > annotated as "flaky"? This would exclude all new tests, by default,
> > and it'd make it clearer which tests need to be fixed.
> > 
> > +1,
> > 
> > If a test in other group which we can confirm it is a flaky test,
> > we can move it to flaky group.
> > 
> > Penghui
> > 
> > On Wed, Mar 9, 2022 at 4:27 AM Michael Marshall 
> > wrote:
> > 
> >> This is a great discussion, thanks for starting it.
> >> 
> >> I support turning off retries for new tests, as Lari suggests.
> >> However, I will point out that this change is not the same as the
> >> initially proposed change to increase the number of times a new test
> >> is run (point (1) in the original email for this thread). I am not
> >> sure if we need to run new tests extra times to test for flakiness,
> >> but I definitely agree that we should not default to retrying newly
> >> added tests.
> >> 
> >> Alternatively, would it be possible to only retry tests that are
> >> annotated as "flaky"? This would exclude all new tests, by default,
> >> and it'd make it clearer which tests need to be fixed.
> >> 
> >>> I see. Now we retry all tests by default. What's the reason?
> >> 
> >> Test retries are enabled precisely because some tests are flaky.
> >> 
> >> Thanks,
> >> Michael
> >> 
> >> 
> >> On Tue, Mar 8, 2022 at 7:57 AM Baozi 
> >> wrote:
> >>> 
> >>> Good job!
> >>> 
> >>> I see. Now we retry all tests by default. What's the reason?
> >>> 
> >>> The process I understand is:
> >>> We don't need to retry the unit test. Once the test fails, let the job
> >> fail.
> >>> The difference is that new or modified tests need to be tested many
> >> times. As long as there is one failure, the job will fail.
> >>> 
>  2022年3月8日 21:0956，Lari Hotari  写道：
>  
>  Here's a PR to disable tests retries for new and modified tests:
>  https://github.com/apache/pulsar/pull/14607
>  
>  Please review and provide feedback.
>  
>  -Lari
>  
>  On 2022/03/08 11:24:13 Lari Hotari wrote:
> > I think this is a good idea. In CI, the tests will be retried multiple
> > times at multiple levels: at the test class / test method level and
> >> at the
> > build level.
> > 
> > I'd like to get rid of test retries completely, since that is the
> >> reason
> > why the flakiness problem gets worse over time. This was also covered
> >> in a
> > proposal that was made about a year ago:
> > 
> >> https://docs.google.com/document/d/10lmn4pW1IsT_8D1ZE0vMjASX0HhjdGdjB794iyScwns/edit
> > .
> > "since the cur

Re: [DISUSS] Improve unit test stability

[Lari Hotari]

> However, I will point out that this change is not the same as the
> initially proposed change to increase the number of times a new test
> is run (point (1) in the original email for this thread). I am not

that's true. Increasing the number of times to run a test method is executed 
could be a breaking change. TestNG supports running each test method multiple 
times (invocationCount parameter on the Test annotation). A lot of the tests 
are stateful and don't support running the test method multiple times without 
resetting state between calls. For test retries, this problem has been solved 
by the TestRetrySupport base class. That was added by PR 
https://github.com/apache/pulsar/pull/9823 and it describes the problem and the 
solution for test retries. 
Running each test class that has been modified multiple times would be a 
solution that would work, but that's not available out-of-the-box in TestNG.
This is the reason why I didn't add the solution to run the test multiple 
times. 
I haven't found a way how to configure TestNG to run certain test classes 
multiple times.  As mentioned above, the built-in solution executes a test 
method multiple times and that might not be supported by the test class. It's 
possible to solve that problem, but it would require some effort.

-Lari

On 2022/03/08 20:26:49 Michael Marshall wrote:
> This is a great discussion, thanks for starting it.
> 
> I support turning off retries for new tests, as Lari suggests.
> However, I will point out that this change is not the same as the
> initially proposed change to increase the number of times a new test
> is run (point (1) in the original email for this thread). I am not
> sure if we need to run new tests extra times to test for flakiness,
> but I definitely agree that we should not default to retrying newly
> added tests.
> 
> Alternatively, would it be possible to only retry tests that are
> annotated as "flaky"? This would exclude all new tests, by default,
> and it'd make it clearer which tests need to be fixed.
> 
> > I see. Now we retry all tests by default. What's the reason?
> 
> Test retries are enabled precisely because some tests are flaky.
> 
> Thanks,
> Michael
> 
> 
> On Tue, Mar 8, 2022 at 7:57 AM Baozi  
> wrote:
> >
> > Good job!
> >
> > I see. Now we retry all tests by default. What's the reason?
> >
> > The process I understand is:
> > We don't need to retry the unit test. Once the test fails, let the job fail.
> > The difference is that new or modified tests need to be tested many times. 
> > As long as there is one failure, the job will fail.
> >
> > > 2022年3月8日 21:0956，Lari Hotari  写道：
> > >
> > > Here's a PR to disable tests retries for new and modified tests:
> > > https://github.com/apache/pulsar/pull/14607
> > >
> > > Please review and provide feedback.
> > >
> > > -Lari
> > >
> > > On 2022/03/08 11:24:13 Lari Hotari wrote:
> > >> I think this is a good idea. In CI, the tests will be retried multiple
> > >> times at multiple levels: at the test class / test method level and at 
> > >> the
> > >> build level.
> > >>
> > >> I'd like to get rid of test retries completely, since that is the reason
> > >> why the flakiness problem gets worse over time. This was also covered in 
> > >> a
> > >> proposal that was made about a year ago:
> > >> https://docs.google.com/document/d/10lmn4pW1IsT_8D1ZE0vMjASX0HhjdGdjB794iyScwns/edit
> > >> .
> > >> "since the current build tolerates flaky tests, the current test retry
> > >> solution leads to more flaky tests being added to the code base over 
> > >> time."
> > >>
> > >> It would be possible to make our CI behave in a way that test method 
> > >> level
> > >> retries are disabled for test classes that are modified or added in a PR.
> > >>
> > >> In GitHub Actions workflows we already have a solution for detecting the
> > >> changed files.
> > >>
> > >>  - name: Detect changed files
> > >>id:   changes
> > >>uses: apache/pulsar-test-infra/paths-filter@master
> > >>with:
> > >>  filters: .github/changes-filter.yaml
> > >>
> > >> It would be possible to make the build work in a way that it passes the
> > >> list of changed tests in a system property or environment variable. This
> > >> could be passed to  org.apache.pulsar.tests.RetryAnalyzer which could be
> > >> modified to disable retries for the tests listed in the parameter that 
> > >> was
> > >> passed via a system property or environment value.
> > >>
> > >> Besides this, it would be necessary to disable the build level test retry
> > >> loop (the build/retry.sh solution) when any test in modified in the 
> > >> module.
> > >> It would be possible to check the failures and skip retrying if one of 
> > >> the
> > >> failures is one of the changed tests.
> > >>
> > >> -Lari
> > >>
> > >>
> > >> On Mon, Mar 7, 2022 at 5:12 AM 包子 
> > >> wrote:
> > >>
> > >>> Hi, I want to discuss how to improve the stability of unit testing.I 
> > >>> found
> > >>> that most flaky unit tes

Re: [ANNOUNCE] New Committer: Andrey Yegorov

[Lari Hotari]

Congrats Andrey!

-Lari

On 2022/03/07 19:25:44 Dave Fisher wrote:
> The Apache Pulsar Project Management Committee (PMC) has invited Andrey 
> Yegorov
> https://github.com/dlg99 to become a committer and we are pleased to
> announce that he has accepted.
> 
> Andrey has made great contributions to Pulsar including Connector and Adaptor 
> work along with updating dependencies for CVEs
> Welcome and Congratulations, Li Li!
> 
> Please join us in congratulating and welcoming Andrey onboard!
> 
> Best Regards,
> Dave Fisher on behalf of the Pulsar PMC

Re: [VOTE][PIP-146] ManagedCursorInfo compression

[Enrico Olivelli]

+1 (binding)

Enrico

Il giorno mer 9 mar 2022 alle ore 13:59 PengHui Li
 ha scritto:
>
> +1
>
> Penghui
>
> On Wed, Mar 9, 2022 at 5:21 PM Zixuan Liu  wrote:
>
> > Discussion thread:
> > https://lists.apache.org/thread/j92bzsby9n2ozc9gcw5psgcy2026l1wm
> >
> > Zixuan Liu  于2022年3月9日周三 17:18写道：
> >
> > > Hi Pulsar community,
> > >
> > > I want to start this PIP - https://github.com/apache/pulsar/issues/14529
> > >
> > > Thanks,
> > > Zixuan
> > >
> > >
> >

RE: Re: [DISCUSS] Releasing pulsar-client-go 0.8.1

[Shubham Sharma (DEVDIV)]

Hi,

We discovered the GPL dependency at Dapr using https://fossa.com/, you can also 
try the same. It can be added in the CI step to prevent introducing any such 
dependencies further.

Thanks,
Shubham

On 2022/03/08 19:44:29 Michael Marshall wrote:
> +1 for releasing 0.8.1. Thanks for starting this discussion, Rui.
>
> Is there any official ASF protocol for dealing with this situation? I
> think we should warn users about the unintended GPL dependency
> included in 0.8.0. Perhaps we can do that by adding a warning to the
> GitHub Release page for 0.8.0 [0] and sending a note to the users
> mailing list?
>
> Also, does Go have any tooling we can add to our release process to
> help prevent this kind of error in future releases?
>
> Thanks,
> Michael
>
> [0] https://github.com/apache/pulsar-client-go/releases/tag/v0.8.0
>
> On Mon, Mar 7, 2022 at 7:59 PM Rui Fu 
> rf...@apache.org wrote:
> >
> > Thanks for all your votings, I will start working on the release.
> >
> > On 2022/03/07 19:14:00 Sijie Guo wrote:
> > > +1
> > >
> > > On Sun, Mar 6, 2022 at 6:46 PM r...@apache.org 
> > > ra...@gmail.com
> > > wrote:
> > >
> > > > +1
> > > >
> > > > --
> > > > Thanks
> > > > Xiaolong Ran
> > > >
> > > > PengHui Li pe...@apache.org 于2022年3月5日周六 
> > > > 18:10写道：
> > > >
> > > > > +1
> > > > >
> > > > > Penghui
> > > > >
> > > > > On Sat, Mar 5, 2022 at 4:58 AM Matteo Merli 
> > > > > ma...@gmail.com
> > > > > wrote:
> > > > >
> > > > > > +1 Thanks Rui, we should eliminate the GPL dependency ASAP.
> > > > > >
> > > > > >
> > > > > >
> > > > > > --
> > > > > > Matteo Merli
> > > > > > ma...@gmail.com
> > > > > >
> > > > > > On Thu, Mar 3, 2022 at 2:08 AM Rui Fu 
> > > > > > rf...@apache.org wrote:
> > > > > > >
> > > > > > > Hi everyone,
> > > > > > >
> > > > > > > I would like to start a discussion here about starting a new 
> > > > > > > release
> > > > of
> > > > > > > pulsar-client-go v0.8.1. Recently we have some of dependencies
> > > > updated
> > > > > > PRs
> > > > > > > from the community, [1] is bumping `github.com/beefsack/go-rate`
> > > > http://github.com/beefsack/go-rate
> > > > > http://github.com/beefsack/go-rate
> > > > > > http://github.com/beefsack/go-rate to the
> > > > > > > latest version, which migrates the license from GPL to MIT. [2] is
> > > > > > bumping `
> > > > > > > github.com/prometheus/client_golang`
> > > > http://github.com/prometheus/client_golang
> > > > > http://github.com/prometheus/client_golang
> > > > > > http://github.com/prometheus/client_golang to address the
> > > > > > CVE-2022-21698. For
> > > > > > > more details, please check the links below.
> > > > > > >
> > > > > > > As the v0.8.0 was just released weeks ago and the next release 
> > > > > > > will
> > > > > start
> > > > > > > about 2 month later, I think we should start the release of 
> > > > > > > v0.8.1.
> > > > > > >
> > > > > > > [1]: https://github.com/apache/pulsar-client-go/pull/735
> > > > > > > [2]: https://github.com/apache/pulsar-client-go/pull/738
> > > > > > >
> > > > > > > --
> > > > > > >
> > > > > > > Best Regards,
> > > > > > >
> > > > > > > Rui Fu
> > > > > >
> > > > >
> > > >
> > >
>

[GitHub] [pulsar-site] Paul-TT commented on a change in pull request #8: Integrating changes from community feedback

[GitBox]

Paul-TT commented on a change in pull request #8:
URL: https://github.com/apache/pulsar-site/pull/8#discussion_r822854239



##
File path: site2/website-next/docusaurus.config.js
##
@@ -143,54 +142,6 @@ module.exports = {
   position: "right",
   label: "Docs",
 },
-{
-  label: "REST APIs",
-  position: "right",
-  items: [
-{
-  label: "Admin REST API",
-  to: "/admin-rest-api",
-},
-{
-  label: "Functions",
-  to: "/functions-rest-api",
-},
-{
-  label: "Sources",
-  to: "/source-rest-api",
-},
-{
-  label: "Sinks",
-  to: "/sink-rest-api",
-},
-{
-  label: "Packages",
-  to: "/packages-rest-api",
-},
-  ],
-},
-{
-  label: "CLI",
-  position: "right",
-  items: [
-{
-  label: "Pulsar Admin",
-  to: "/pulsar-admin-cli",
-},
-{
-  label: "Pulsar Client",
-  to: "/pulsar-client-cli",
-},
-{
-  label: "Pulsar Perf",
-  to: "/pulsar-perf-cli",
-},
-{
-  label: "Pulsar",
-  to: "/pulsar-cli",
-},
-  ],
-},

Review comment:
   @urfreespace  On the website weekly meeting yesterday, it was been 
decided that these links will be added to the docs and removed from the nav. 




-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@pulsar.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [pulsar-site] Paul-TT commented on a change in pull request #8: Integrating changes from community feedback

[GitBox]

Paul-TT commented on a change in pull request #8:
URL: https://github.com/apache/pulsar-site/pull/8#discussion_r822855773



##
File path: site2/website-next/src/theme/Navbar/index.js
##
@@ -307,13 +307,7 @@ function Navbar() {
   setVersion(latestStableVersion);
 }}
   />
-  
-{() => (
-  
-{getVersion() == "master" ? "next" : getVersion()}
-  
-)}
-  
+

Review comment:
   @urfreespace  On the website weekly meeting yesterday, it was decided 
this would be removed




-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@pulsar.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [pulsar-site] Paul-TT commented on a change in pull request #8: Integrating changes from community feedback

[GitBox]

Paul-TT commented on a change in pull request #8:
URL: https://github.com/apache/pulsar-site/pull/8#discussion_r822858186



##
File path: site2/website-next/docusaurus.config.js
##
@@ -254,28 +205,10 @@ module.exports = {
   position: "right",
 },
 {
-  label: "Version",
-  to: "/docs",
-  position: "right",
-  items: [
-{
-  label: "2.9.0",
-  to: "/docs/2.9.0/",
-},
-{
-  label: "2.8.0",
-  to: "/docs/2.8.0/",
-},
-{
-  label: "2.7.0",
-  to: "/docs/2.7.0/",
-},
-{
-  label: "2.6.0",
-  to: "/docs/2.6.0/",
-},
-  ],
-},
+  to: '/download',

Review comment:
   @urfreespace  On the website weekly meeting yesterday, this change was 
confirmed




-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@pulsar.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

KEYS file update

[Dave Fisher]

We have two KEYS files stored on https://dist.apache.org one in the Release 
directory and one in the Dev directory.

Apache Release Distribution Policy 
(https://infra.apache.org/release-download-pages.html) requires and on the 
Download page (https://pulsar.apache.org/en/download/) we refer to 
https://downloads.apache.org/pulsar/KEYS which is correct.

However all of our recent releases are signed with the file here 
https://dist.apache.org/repos/dist/dev/pulsar/KEYS

The wiki on releases needs to indicate that we should update the release keys 
and never remove a key the has ever been used to sign a Pulsar release. These 
updates need to be done by a PMC member.

I have merged the dev KEYS into the release KEYS.

% gpg --import KEYS
gpg: key 7B6A6401BF99B4A3: "Matteo Merli (CODE SIGNING KEY) 
" not changed
gpg: key C238A8CAAC055FD2: "Matteo Merli " not changed
gpg: key 3956248899767A23: "rdhabalia " not changed
gpg: key F260D7EDE4EECE23: "Joe Francis (CODE SIGNING KEY) " 
not changed
gpg: key A92D27AAC3D80414: "Nozomi Kurihara (CODE SIGNING KEY) 
" not changed
gpg: key C8A00D9222DE9ECF: "Yuki Shiga (CODE SIGNING KEY) " 
not changed
gpg: key 167F106C5D529B4D: "Masahiro Sakamoto (CODE SIGNING KEY) 
" not changed
gpg: key CF2A679717747AD4: "Hiroyuki Sakai (CODE SIGNING KEY) 
" not changed
gpg: key 7BA1A64CBBC114EC: "Jai Asher (CODE SIGNING KEY) " not 
changed
gpg: key 5B3FBDB4FD74402C: "Sijie Guo " not changed
gpg: key C69517E5621D7F5F: "Jerry Peng (CODE SIGNING KEY) 
" not changed
gpg: key 772D77990D717CBC: "Penghui Li (CODE SIGNING KEY) " 
not changed
gpg: key BC86116ED3F5E291: "Jia Zhai (3...) " not changed
gpg: key C238A8CAAC055FD2: "Matteo Merli " not changed
gpg: key 3956248899767A23: "rdhabalia " not changed
gpg: key F260D7EDE4EECE23: "Joe Francis (CODE SIGNING KEY) " 
not changed
gpg: key A92D27AAC3D80414: "Nozomi Kurihara (CODE SIGNING KEY) 
" not changed
gpg: key C8A00D9222DE9ECF: "Yuki Shiga (CODE SIGNING KEY) " 
not changed
gpg: key 167F106C5D529B4D: "Masahiro Sakamoto (CODE SIGNING KEY) 
" not changed
gpg: key CF2A679717747AD4: "Hiroyuki Sakai (CODE SIGNING KEY) 
" not changed
gpg: key 7BA1A64CBBC114EC: "Jai Asher (CODE SIGNING KEY) " not 
changed
gpg: key 5B3FBDB4FD74402C: "Sijie Guo " not changed
gpg: key C69517E5621D7F5F: "Jerry Peng (CODE SIGNING KEY) 
" not changed
gpg: key 577C07CA867AE910: "guangning (Apache Committer) 
" not changed
gpg: key B49DF828AFC9A442: "xiaolong (CODE SIGNING KEY) " not 
changed
gpg: key FAAF93DC8E90A118: "Yong Zhang (APACHE CODE SIGNING KEY) 
" not changed
gpg: key BC86116ED3F5E291: "Jia Zhai (3...) " not changed
gpg: key 577C07CA867AE910: "guangning (Apache Committer) 
" not changed
gpg: key B49DF828AFC9A442: "xiaolong (CODE SIGNING KEY) " not 
changed
gpg: key FAAF93DC8E90A118: "Yong Zhang (APACHE CODE SIGNING KEY) 
" not changed
gpg: key DC08637CA615D22C: "Enrico Olivelli " not changed
gpg: key 6B59B6A7804AB38D: "Addison Higham (CODE SIGNING KEY) 
" not changed
gpg: key D3FA67D522C55256: "Lari Hotari (CODE SIGNING KEY) 
" not changed
gpg: key E8D2ED3D0C2FA918: "congbo " not changed
gpg: key 7408747E09CAB5E5: "congbo (congbobo184) " not 
changed
gpg: key 6BD513735EDFBA3A: "bogong (congbobo184) " not 
changed
gpg: key A641378C97944D34: public key "chenhang (CODE SIGNING KEY) 
" imported
gpg: key 2C9C4267F240F95A: public key "Chris Kellogg (CODE SIGNING KEY) 
" imported
gpg: key 249DF015663A88B9: public key "linlin " imported
gpg: key 61931C9DB84C4F2A: public key "technoboy (CODE SIGNING KEY) 
" imported
gpg: key 61931C9DB84C4F2A: "technoboy (CODE SIGNING KEY) 
" not changed
gpg: key 46F42383EB24F7AA: public key "ran gao " imported
gpg: key BC33A6A32F90D558: public key "ran gao (CODE SIGNING KEY) 
" imported
gpg: key C5724B3F5588C4EB: public key "Michael Marshall " 
imported
gpg: key BC8E5EDA35763362: public key "Li Li (CODE SIGNING KEY) 
" imported
gpg: key 5847FC5592B9FCC8: public key "Rui Fu (CODE SIGNING KEY) 
" imported
gpg: Total number processed: 46
gpg:   imported: 9
gpg:  unchanged: 37

All the best,
Dave

Re: KEYS file update

[Enrico Olivelli]

Thanks
I believe that probably the problem comes from the fact that committers
don't have write access to 'dist' and new RMs need to add their keys.

We should document better the process and stop using 'dev'

Enrico

Il Mer 9 Mar 2022, 20:28 Dave Fisher  ha scritto:

> We have two KEYS files stored on https://dist.apache.org one in the
> Release directory and one in the Dev directory.
>
> Apache Release Distribution Policy (
> https://infra.apache.org/release-download-pages.html) requires and on the
> Download page (https://pulsar.apache.org/en/download/) we refer to
> https://downloads.apache.org/pulsar/KEYS which is correct.
>
> However all of our recent releases are signed with the file here
> https://dist.apache.org/repos/dist/dev/pulsar/KEYS
>
> The wiki on releases needs to indicate that we should update the release
> keys and never remove a key the has ever been used to sign a Pulsar
> release. These updates need to be done by a PMC member.
>
> I have merged the dev KEYS into the release KEYS.
>
> % gpg --import KEYS
> gpg: key 7B6A6401BF99B4A3: "Matteo Merli (CODE SIGNING KEY) <
> mme...@apache.org>" not changed
> gpg: key C238A8CAAC055FD2: "Matteo Merli " not changed
> gpg: key 3956248899767A23: "rdhabalia " not changed
> gpg: key F260D7EDE4EECE23: "Joe Francis (CODE SIGNING KEY) <
> j...@apache.org>" not changed
> gpg: key A92D27AAC3D80414: "Nozomi Kurihara (CODE SIGNING KEY) <
> nkuri...@apache.org>" not changed
> gpg: key C8A00D9222DE9ECF: "Yuki Shiga (CODE SIGNING KEY) <
> yush...@apache.org>" not changed
> gpg: key 167F106C5D529B4D: "Masahiro Sakamoto (CODE SIGNING KEY) <
> massa...@apache.org>" not changed
> gpg: key CF2A679717747AD4: "Hiroyuki Sakai (CODE SIGNING KEY) <
> hrsa...@apache.org>" not changed
> gpg: key 7BA1A64CBBC114EC: "Jai Asher (CODE SIGNING KEY) "
> not changed
> gpg: key 5B3FBDB4FD74402C: "Sijie Guo " not changed
> gpg: key C69517E5621D7F5F: "Jerry Peng (CODE SIGNING KEY) <
> jerryp...@apache.org>" not changed
> gpg: key 772D77990D717CBC: "Penghui Li (CODE SIGNING KEY) <
> peng...@apache.org>" not changed
> gpg: key BC86116ED3F5E291: "Jia Zhai (3...) " not
> changed
> gpg: key C238A8CAAC055FD2: "Matteo Merli " not changed
> gpg: key 3956248899767A23: "rdhabalia " not changed
> gpg: key F260D7EDE4EECE23: "Joe Francis (CODE SIGNING KEY) <
> j...@apache.org>" not changed
> gpg: key A92D27AAC3D80414: "Nozomi Kurihara (CODE SIGNING KEY) <
> nkuri...@apache.org>" not changed
> gpg: key C8A00D9222DE9ECF: "Yuki Shiga (CODE SIGNING KEY) <
> yush...@apache.org>" not changed
> gpg: key 167F106C5D529B4D: "Masahiro Sakamoto (CODE SIGNING KEY) <
> massa...@apache.org>" not changed
> gpg: key CF2A679717747AD4: "Hiroyuki Sakai (CODE SIGNING KEY) <
> hrsa...@apache.org>" not changed
> gpg: key 7BA1A64CBBC114EC: "Jai Asher (CODE SIGNING KEY) "
> not changed
> gpg: key 5B3FBDB4FD74402C: "Sijie Guo " not changed
> gpg: key C69517E5621D7F5F: "Jerry Peng (CODE SIGNING KEY) <
> jerryp...@apache.org>" not changed
> gpg: key 577C07CA867AE910: "guangning (Apache Committer) <
> guangn...@apache.org>" not changed
> gpg: key B49DF828AFC9A442: "xiaolong (CODE SIGNING KEY) "
> not changed
> gpg: key FAAF93DC8E90A118: "Yong Zhang (APACHE CODE SIGNING KEY) <
> y...@apache.org>" not changed
> gpg: key BC86116ED3F5E291: "Jia Zhai (3...) " not
> changed
> gpg: key 577C07CA867AE910: "guangning (Apache Committer) <
> guangn...@apache.org>" not changed
> gpg: key B49DF828AFC9A442: "xiaolong (CODE SIGNING KEY) "
> not changed
> gpg: key FAAF93DC8E90A118: "Yong Zhang (APACHE CODE SIGNING KEY) <
> y...@apache.org>" not changed
> gpg: key DC08637CA615D22C: "Enrico Olivelli " not
> changed
> gpg: key 6B59B6A7804AB38D: "Addison Higham (CODE SIGNING KEY) <
> addis...@apache.org>" not changed
> gpg: key D3FA67D522C55256: "Lari Hotari (CODE SIGNING KEY) <
> lhot...@apache.org>" not changed
> gpg: key E8D2ED3D0C2FA918: "congbo " not changed
> gpg: key 7408747E09CAB5E5: "congbo (congbobo184) " not
> changed
> gpg: key 6BD513735EDFBA3A: "bogong (congbobo184) " not
> changed
> gpg: key A641378C97944D34: public key "chenhang (CODE SIGNING KEY) <
> chenh...@apache.org>" imported
> gpg: key 2C9C4267F240F95A: public key "Chris Kellogg (CODE SIGNING KEY) <
> cckell...@apache.org>" imported
> gpg: key 249DF015663A88B9: public key "linlin "
> imported
> gpg: key 61931C9DB84C4F2A: public key "technoboy (CODE SIGNING KEY) <
> techno...@apache.org>" imported
> gpg: key 61931C9DB84C4F2A: "technoboy (CODE SIGNING KEY) <
> techno...@apache.org>" not changed
> gpg: key 46F42383EB24F7AA: public key "ran gao " imported
> gpg: key BC33A6A32F90D558: public key "ran gao (CODE SIGNING KEY) <
> r...@apache.org>" imported
> gpg: key C5724B3F5588C4EB: public key "Michael Marshall <
> mmarsh...@apache.org>" imported
> gpg: key BC8E5EDA35763362: public key "Li Li (CODE SIGNING KEY) <
> urf...@apache.org>" imported
> gpg: key 5847FC5592B9FCC8: public key "Rui Fu (CODE SIGNING KEY) <
> r...@apache.org>" imported
> gpg: Total number processed: 46
> g

Re: [VOTE] Pulsar Release 2.8.3 Candidate 4

[Michael Marshall]

Update on publishing this release.

First, the binaries are now promoted:
https://dist.apache.org/repos/dist/release/pulsar/pulsar-2.8.3/.
Thanks, Dave!

Can I get some help from someone with special DockerHub permission to
publish the following docker images to our official repo?

michaelmarshall/pulsar:2.8.3-rc4
michaelmarshall/pulsar-all:2.8.3-rc4
michaelmarshall/pulsar-standalone:2.8.3-rc4
michaelmarshall/pulsar-grafana:2.8.3-rc4

For building the python OSX packages, I am hitting the error described
in this issue: https://github.com/apache/pulsar/issues/13429. I am
building on MacOS. I'd appreciate any help you can give.

Here is a draft of the release notes:
https://github.com/apache/pulsar/pull/14632. Feel free to give
feedback on the PR.

Thanks,
Michael

On Wed, Mar 9, 2022 at 12:36 AM Michael Marshall  wrote:
>
> Thank you for the validation.
>
> Closing this vote with 3 +1(binding) votes.
>
> I plan to start the subsequent release work tomorrow.
>
> Thanks,
> Michael
>
>
> On Mon, Mar 7, 2022 at 7:48 PM PengHui Li  wrote:
> >
> > +1 (binding)
> >
> > - Checked signatures
> > - Run standalone, publish/consume messages
> > - Checked connector and stateful function
> >
> > Penghui
> >
> >
> > On Mon, Mar 7, 2022 at 7:28 PM Enrico Olivelli  wrote:
> >
> > > +1 (binding)
> > > - verified checksums, signatures, RAT, spotbugs...(using JDK11 on Mac)
> > > - built the docker image
> > > - built a couple of applications and run their tests
> > > - run tests of a few applications using the Docker image (built from
> > > source), those tests cover a good part of Transactions Java client
> > > usages and Pulsar IO
> > > - run Jakarta JMS 2.0 TCK (technology compatibility kit)
> > >
> > > Thank you very much Michael
> > >
> > > Enrico
> > >
> > >
> > > Il giorno lun 7 mar 2022 alle ore 09:25 Masahiro Sakamoto
> > >  ha scritto:
> > > >
> > > > +1 (binding)
> > > >
> > > > - Checked checksums and signatures
> > > > - Checked license headers using Apache Rat
> > > > - Compiled the source
> > > > - Ran the standalone server
> > > > - Confirmed that producer and consumer work properly
> > > > - Validated functions, connectors, and stateful functions
> > > >
> > > > Regards,
> > > >
> > > > Masahiro Sakamoto
> > > > Yahoo Japan Corp.
> > > > E-mail: massa...@yahoo-corp.jp
> > > >
> > > > -Original Message-
> > > > From: Michael Marshall 
> > > > Sent: Thursday, March 3, 2022 2:33 PM
> > > > To: Dev 
> > > > Subject: [VOTE] Pulsar Release 2.8.3 Candidate 4
> > > >
> > > > This is the third release candidate for Apache Pulsar, version 2.8.3.
> > > >
> > > > It fixes the following issues:
> > > > https://github.com/apache/pulsar/compare/v2.8.2...v2.8.3-candidate-4
> > > >
> > > > *** 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 source (tag), binaries are provided for
> > > convenience.
> > > >
> > > > Source and binary files:
> > > > https://dist.apache.org/repos/dist/dev/pulsar/pulsar-2.8.3-candidate-4/
> > > >
> > > > There are many checksums and signatures to validate, including
> > > apache-pulsar-2.8.3-bin.tar.gz, apache-pulsar-2.8.3-src.tar.gz,
> > > apache-pulsar-offloaders-2.8.3-bin.tar.gz, and all of the connectors.
> > > > All are located here:
> > > > https://dist.apache.org/repos/dist/dev/pulsar/pulsar-2.8.3-candidate-4/.
> > > >
> > > > Unofficial Docker images:
> > > > michaelmarshall/pulsar:2.8.3-rc4
> > > > michaelmarshall/pulsar-all:2.8.3-rc4
> > > > michaelmarshall/pulsar-standalone:2.8.3-rc4
> > > > michaelmarshall/pulsar-grafana:2.8.3-rc4
> > > >
> > > > Maven staging repo:
> > > > https://repository.apache.org/content/repositories/orgapachepulsar-1145/
> > > >
> > > > The tag to be voted upon:
> > > > v2.8.3-candidate-4 (ee87c7d6c20186ae59298a9a9ec1fdb2b09954c7)
> > > > https://github.com/apache/pulsar/releases/tag/v2.8.3-candidate-4
> > > >
> > > > Pulsar's KEYS file containing PGP keys we use to sign the release:
> > > > https://dist.apache.org/repos/dist/dev/pulsar/KEYS
> > > >
> > > > Please download the source package, and follow the README to build and
> > > run the Pulsar standalone service.
> > >

[GitHub] [pulsar-site] urfreespace merged pull request #8: Integrating changes from community feedback

[GitBox]

urfreespace merged pull request #8:
URL: https://github.com/apache/pulsar-site/pull/8


   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@pulsar.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [pulsar-site] urfreespace opened a new pull request #16: feat: change releases-notes to release-notes

[GitBox]

urfreespace opened a new pull request #16:
URL: https://github.com/apache/pulsar-site/pull/16


   Signed-off-by: LiLi 


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@pulsar.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [pulsar-site] urfreespace merged pull request #16: feat: change releases-notes to release-notes

[GitBox]

urfreespace merged pull request #16:
URL: https://github.com/apache/pulsar-site/pull/16


   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@pulsar.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org