Re: 回复: [Discuss] PIP-190: Simplify Pulsar documentation release and maintenance strategy
+1, Good idea! Thanks, Zixuan Enrico Olivelli 于2022年7月27日周三 14:13写道： > Yu > > Il Mer 27 Lug 2022, 05:33 Liu Yu ha scritto: > > > +1 for this proposal since it improves the efficiency of managing docs. > > > > We'll take it as we reach a lazy consensus and implement this plan if > > there is no objection until tomorrow. > > > > This is a PIP so we must wait for a explicit approval by running a VOTE. > > If you wanted to go with lazy consensus then we shouldn't have started this > thread > > Enrico > > > > > On 2022/07/25 09:13:50 M Jun wrote: > > > Hi Asaf, > > > > > > The doc files for all older versions are independent copies, stored at > > > https://github.com/apache/pulsar/tree/master/site2/website/versioned_docs. > > > > > > For example, the doc for 2.10.0 was a copy saved from the next (master) > > doc at that milestone. > > > > > > 发件人: Asaf Mesika > > > 发送时间: 2022年7月24日 21:00 > > > 收件人: dev@pulsar.apache.org > > > 主题: Re: [Discuss] PIP-190: Simplify Pulsar documentation release and > > maintenance strategy > > > > > > If I understand correctly, using tags, you can automatically create the > > > docs for the next minor version? > > > So for older minor versions, where those files will be at? using tags > > from > > > git? > > > > > > On Sat, Jul 23, 2022 at 7:04 AM Ma Jun wrote: > > > > > > > Hi, Pulsar community, > > > > > > > > Happy weekend! > > > > > > > > I'd like to open a discussion about PIP-190: Simplify Pulsar > > documentation > > > > release and maintenance strategy. > > > > > > > > Proposal link: https://github.com/apache/pulsar/issues/16637. > > > > > > > > > > > > > > > - > > > > > > > > ## Motivation > > > > > > > > This proposal is focused on improving and simplifying the release and > > > > maintenance strategy of the existing Apache Pulsar documentation. > > > > > > > > In general, this proposal provides equal values and a better user > > > > experience without sacrificing unpredictable efforts in the release > and > > > > maintenance process. The benefits include: > > > > * Improve user experience when they look for the documentation of a > > > > specific release. > > > > * Optimize the doc development and release process for bug-fix > > releases: > > > >* Turn doc development for bug-fix releases from post-release into > > > > just-in-time. > > > >* Save Release Manager’s effort in generating doc files for > bug-fix > > > > releases. > > > > * Save a great amount of the community’s effort in syncing doc > > > > improvements and fixes to historical doc versions that are in the > > > > maintenance cycle. > > > > > > > > > > > > Since there are quite a few illustrations and links in this > proposal, I > > > > didn't copy and paste the complete content into this email thread. > You > > can > > > > access the GitHub link to review the proposal with a better view. > > > > > > > > > > > > Cheers! > > > > > > > > momo-jun > > > > > > > > > > > > > >
Re: [VOTE] PIP-190: Simplify Pulsar documentation release and maintenance strategy
+1 since it improves the efficiency of managing docs. On Thu, Jul 28, 2022 at 8:16 AM M Jun wrote: > Hi, Pulsar community, > > I'd like to start a vote on PIP-190: Simplify Pulsar documentation release > and maintenance strategy. > > You can find the proposal at https://github.com/apache/pulsar/issues/16637 > and the discussion thread at > https://lists.apache.org/thread/g5b8lcwtn10ox7vd67n31om9w1rxn4l7. > > The vote will stay open for at least 48 hours. > > > Cheers, > momo-jun >
[VOTE] PIP-190: Simplify Pulsar documentation release and maintenance strategy
Hi, Pulsar community, I'd like to start a vote on PIP-190: Simplify Pulsar documentation release and maintenance strategy. You can find the proposal at https://github.com/apache/pulsar/issues/16637 and the discussion thread at https://lists.apache.org/thread/g5b8lcwtn10ox7vd67n31om9w1rxn4l7. The vote will stay open for at least 48 hours. Cheers, momo-jun
[GitHub] [pulsar-site] hrsakai closed pull request #150: Fix default value of logSizeLimit
hrsakai closed pull request #150: Fix default value of logSizeLimit URL: https://github.com/apache/pulsar-site/pull/150 -- 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] hrsakai commented on pull request #150: Fix default value of logSizeLimit
hrsakai commented on PR #150: URL: https://github.com/apache/pulsar-site/pull/150#issuecomment-1197470431 @urfreespace I see.Thanks. -- 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: [ANNOUNCE] Micheal Marshall as a new PMC member in Pulsar
Congratulations! Well deserved! > On Jul 26, 2022, at 11:21 AM, Enrico Olivelli wrote: > > I am glad to announce that the Apache Pulsar PMC invited Micheal to > join the PMC and he accepted. > > Micheal is doing a great job in stewarding our community > > Please join me and celebrate ! > > Enrico Olivelli
Re: [DISCUSS] PIP-195: New bucket based delayed message tracker
Hi Enrico, Thanks for your feedback. > How do you enable this feature? A flag in broker.conf? Yes, we add a flag in broker.conf to enable this feature, I will update it > Is it possible to enable the feature by doing a rolling upgrade of the > brokers? What happens if you have brokers that are still running the old > tracker? I think it is possible to enable the feature by doing a rolling upgrade of the brokers, because the delayed message index in the old tracker only exists in the memory. > Is it possible to rollback seamlessly? It is possible to rollback seamlessly, the old memory tracker will rebuild the delayed message index. On 2022/07/27 06:19:28 Enrico Olivelli wrote: > Good proposal. > > How do you enable this feature? A flag in broker.conf? > > Is it possible to enable the feature by doing a rolling upgrade of the > brokers? What happens if you have brokers that are still running the old > tracker? > > Is it possible to rollback seamlessly? > > Enrico > > Il Mer 27 Lug 2022, 05:39 Dezhi Liu ha scritto: > > > +1, good job. > > > > Thanks, > > Dezhi > > > > On 2022/07/25 02:22:00 Cong Zhao wrote: > > > Hello Pulsar Community, > > > > > > > > > I would like to open a discussion here about PIP-195 : New bucket based > > > delayed message tracker. I look forward to your feedback. > > > > > > > > > PIP: https://github.com/apache/pulsar/issues/16763 > > > > > > > > > Thanks, > > > > > > Cong Zhao > > > > > > Thanks, Cong Zhao
Re: [DISCUSS] PIP 194 : Pulsar client: seek command add epoch
Thanks Zike. > > - stage 1: Check the current cursor status when handling flowPermits from > > the server side. > > Could you explain more details on this step? It looks like there is not much described above. What kind of status needs to be checked, and what kind of behavior will the broker take? It is necessary to check the current cursor status when handling flowPermits request from the server side. If the server is handling seek request, it should ignore flowPermits request because the request is illegal. > > 1. Consumer reconnect need reset epoch. >> Why do we need to reset the epoch when the consumer reconnects? The reconnected consumer can regard as a new consumer with new epoch.
Re: [DISCUSS] Restart Release Pulsar 2.7.5
Hi all, > There are 4 closed PRs targeting 2.7.5 that have not yet been cherry-picked > [4]. I'll follow up on these PRs and solve the test regression issue and start > preparing branch-2.7 RC2 for the release. After dealing with these 4 closed PRs, I find that - There are 2 open PRs (#11992 and #16326) targeting branch-2.7 but not labeled with "release/2.7.5". - There are 4 open PRs and 17 merged PRs labeled "release/2.7.6" but have not yet been cherry-picked. See [1]. As we plan to set 2.7.5 as the final release of branch 2.7, all these PRs will be included in this release, and labeled "release/2.7.5". Please let me know if I miss other PRs. BR, Haiting [1] https://github.com/apache/pulsar/pulls?q=is%3Apr+label%3Arelease%2F2.7.6+-label%3Acherry-picked%2Fbranch-2.7+ On 2022/07/26 11:19:49 Haiting Jiang wrote: > Hello Pulsar Community, > > Previously in early February, we had a discussion about 2.7.5 release in [1]. > But unfortunately, there seems to be a test regression in Candidate 1 and the > release process is blocked since [2]. I would like to pick up the work and > volunteer to be the release manager. > > Here [3] you can find the list of 52 commits to branch-2.7 since the 2.7.4 > release. The commits number is 41 more than RC1. Since 2.7.5 should be the > last release of branch 2.7, I plan to include all existing commit this time. > After that branch 2.7 should not accept any more commits. > > There are 4 closed PRs targeting 2.7.5 that have not yet been cherry-picked > [4]. I'll follow up on these PRs and solve the test regression issue and start > preparing branch-2.7 RC2 for the release. > > BR, > Haiting Jiang > > [1] https://lists.apache.org/thread/wxl5z67nnzv05r5vldjq3c6sm7fxnrcc > [2] https://lists.apache.org/thread/yvrmwldtzbo9lbs0jqjfj31lxtd792jq > [3] https://github.com/apache/pulsar/compare/v2.7.4...branch-2.7 > [4] > https://github.com/apache/pulsar/pulls?q=is%3Apr+label%3Arelease%2F2.7.5+-label%3Acherry-picked%2Fbranch-2.7 >
Re: svn commit: r55993 - /release/pulsar/KEYS
Thank you! Sent from my iPhone > On Jul 27, 2022, at 5:01 AM, peng...@apache.org wrote: > > Author: penghui > Date: Wed Jul 27 09:01:00 2022 > New Revision: 55993 > > Log: > Added gpg key for jianghaiting > > Modified: >release/pulsar/KEYS > > Modified: release/pulsar/KEYS > == > --- release/pulsar/KEYS (original) > +++ release/pulsar/KEYS Wed Jul 27 09:01:00 2022 > @@ -2565,3 +2565,62 @@ KYjUi0vMV8veMbxZ3Zc97ne5fahdcWPztxP1OR5H > tapm1Fb4EP22EkzOBifa+yDpAn1HIGaK0cInhg== > =mtfc > -END PGP PUBLIC KEY BLOCK- > +pub rsa4096 2022-07-27 [SC] > + 0251E6BBD8AB43076CFFD5F4BF8EDF4540A321C4 > +uid [ unknown] Haiting Jiang (CODE SIGNING KEY) > > +sig 3BF8EDF4540A321C4 2022-07-27 Haiting Jiang (CODE SIGNING KEY) > > +sub rsa4096 2022-07-27 [E] > +sig BF8EDF4540A321C4 2022-07-27 Haiting Jiang (CODE SIGNING KEY) > > + > +-BEGIN PGP PUBLIC KEY BLOCK- > + > +mQINBGLgtkYBEADDXQKIt/EYYJc56AmnfpKnpdffiQDnG2dMES7pSNi74sAOEwlG > +19uSE9Uyp6skXTdPKpLkFMne8EAbulif0BH8NkW3SGkWoIhbZEBVFhi5yVGjYVph > +OrDGa/beSvo2p53dDnfCQY4OaN4ujsrmRzMxU+CXX4ijiIsZOIcK0anhn2SRrEEW > +xuBxfHD88eCBzUb0i1V5N6Tt4semq7W100nJk56HFajm/ski+HLWuYIs4tJ9Cf8H > +tmb9Vd8AYAgAjJcSTysJEOpgp9cMIxeBgMxjxYiS8gOQ8ALFAp/RfMWBIIazVwly > +M1wl+uKQHrrxq2KHF5il1PMccdEfLlb7W+/FdwWtJONYcjN0562Kk46EHMTcrW76 > +q9XM9rdrr6dEpeB63HG9OZ9cAzHiGxJsqd9go9u3GFQy8xUASS2W+T57BIygbySs > +afmpyBU5MvQ/a2x8ejjVdBs+pSga9vnUsXvErYf+MK56/l9/JC6eaIhUjLbbDWY5 > +ieSsB9HXIKAuvhdtTrNOKY4QoNvXqXeWXGLw6oj9DjblxuI9ZfpM3Q45BY+y+FpL > +eVuNIEff+XdOeK+hGBgVa4HKPinurQ/2JmK/fzbGh+D/fbFPsdW1DYX2UZs+doGz > +VcOBuaKKYbbtvBTfxsTPpUOWS6ptVNcHA473u3s2KNN+HSueU/P2Ah2YDwARAQAB > +tDpIYWl0aW5nIEppYW5nIChDT0RFIFNJR05JTkcgS0VZKSA8amlhbmdoYWl0aW5n > +QGFwYWNoZS5vcmc+iQJSBBMBCAA8FiEEAlHmu9irQwds/9X0v47fRUCjIcQFAmLg > +tkYCGwMFCwkIBwIDIgIBBhUKCQgLAgQWAgMBAh4HAheAAAoJEL+O30VAoyHEG48P > +/1Jd4uN8LQcCH6kkXfMxEs8jbfcgN8arwvG4UJI/Cbnk0/revpiGnorjKJb/bKhq > +Bptajek1l7t2DAhRnpwpBDFKmpkzs3ZpvxCZUaU3kU108zonRm0rK4rDsd+RAu/x > +QhcLtYrklOmnmNtvrUDneRrgx3slO1Y+QVFzXtcWYUrZu5JQhQSL8F29h8EcZ+MH > +A2A6cIgab5EPTU1bBDBlt0JU8t/D2FMjW8vSgn6ylEVxTjpQeQqi1XRO8pOl+Uuk > ++Scu9dvjgTzJZooMQqf+9cQA2Pg9pTHdPiXYHxx6eKa1ATml7OfyGzvxCaNyRFhS > +HZasqV48U0mk7oYyWyVKNMq7oCDEItOU5OBudmCiz3MtTxJEbZKIRMul6h2r6/1H > +PBHvq9ifzbi3dfONXDk8d5a7ilmqX40/ZrxLXbRSLZ3jkpwcUd25ZfksaT/vFo87 > +GLkA2r/L8iiskux/OPmNcktd3TtPltJaRVUMyBycn6QuPOcJ9NV7KiyLRMyD79S+ > +UbqU/8ESUjQxoRegnHCixIZf4T5i/m7fkWdSvyW0SQ5vFJakPM3rvzdYROMM6t7H > +1WPLcVqvlpHZ3oG2koyh3JfVSzPUkzgzZ9f6BjK1y/1eHRuvffhoGWZwbGTjMNXf > +G1OeSkZkR9DPLbYUHhKqYfKpt4JpqAgkww5t99gTl+yquQINBGLgtkYBEACmxhSI > +c7DGhQiPzNIiYUs8jN7t3eORMCRZfI5FVgw2zL9vt9f+UB8hjIhvXToE/ASrdLlh > +utG33BIYD0aBmExL0UICyFfQR36AM1grlGH5NJXJqm8sHn3GDdf8z9qHncElosXb > +gevNFHY45IviTmn2q96QGDwIbP5fRLROWC8guNLld6oDWeTfNVxmNxoMEKHA4L6v > +mnItgR0JRE/TzNQ5CBm1BW1mLF2HNv7MZH39W3nXz6N1GPh+M6NSeL2kfrs9RqPG > +STbi1fTuvfDqbio1DymtjDLUVg8hH1LxgF07gf9eXbnopipQNsZ1SRJ5jx0/4/dy > +MOLnqiNcJXrjbwgGMh3r9eigtudT5MImvBaaFwLyd1jC1pJvlp03xOVwZ4+KkCNO > +7ZAQ3i81tWwtZJ38rxXdLKziXViunFFe9647nB0iNzrtpnZptAp2bGX1L95/bZVk > +1nDS7BuiihxW19CX5Yvzjh66D+9BkORw/Sx9FJ74O8c/6fxPDLrNWaMriVHom4VS > +Q5L7FwyKBqMzgC0cn3F3KTSl1hJSZoNWJPbVMIQvFGgCFXqM7AyRJFE96vAm+GTl > +aknF7WuRuHDPKH+iEn/0FCWcHYxjEvTWjWkbJDF1LZiGRbNyu4NoixhRfpyJB4pb > +uQEjVwVVVqvtd32RRZoAZtlo8JjGsbfai+0wpwARAQABiQI2BBgBCAAgFiEEAlHm > +u9irQwds/9X0v47fRUCjIcQFAmLgtkYCGwwACgkQv47fRUCjIcSi6Q//TSf2l0qr > +ReU3JFbOfT40cORmL3hZFUOq+r68Z7DaaKHSLj2W1WlITvoci5C9F1Gq0a9MOEx5 > +sbIA+EKBcj8oef0aOYW1zZK0iG/uwYOOWaHXWxqwxeOBeFNQthblI5ereakoRHIv > +n5mKPmr0dVf1TDBaMqldvUiX7iWzEYNshUCZ/rCLj1L7SreRhurTd1TOnCqr690f > +2B2yMFVoHak4zX5mjCp3vF+wmbjwYN+gNUuBFbbVa9f7kA4k39RMGP0TfshEImle > +EZXDSabh8iSnoJhDZ/brHB+h9Qv4QzZkXGDF5tgaROwZynB7hbU6JwOlcwkzXVXY > +tV/ml+AeVWwpQwgdrT+gr6b56e+EW7WQuVNJD0Ikh2zq5i2tiS3L/0+Xg8Pufkx2 > +mU1CNOV5EKI7+14Uip1uxxTuB+PrcGETfEXStCkEurqRck5hPSwIWiCHAXoLugaa > +YOGbllERPrT8IEuHvy4Ms5QTpXY2oqb0CTACM9Rw6nq4BbSUg8BrSJEFVZyM38g8 > +6nwLnYZ95YysiI9gMnPlMQwfXiGGpFfTqVjqFXGkiARwgHEJVowt2D+dIIBL+Xng > +htxsoZFlytQLr3QDgmCYCC+cKrUYoYE1R4syhrBqiUuJljwTUkizyyGepYP18pow > +U0tcn7seso2XnG8DuIORm0tb5QfvueQzbM8= > +=YSQC > +-END PGP PUBLIC KEY BLOCK- > >
[GitHub] [pulsar-site] urfreespace merged pull request #153: update event about san-francisco-2022 summmit
urfreespace merged PR #153: URL: https://github.com/apache/pulsar-site/pull/153 -- 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: [ANNOUNCE] Micheal Marshall as a new PMC member in Pulsar
Congratulations, Micheal !!! Max Xu 于2022年7月27日周三 14:08写道： > Congratulations, Michael ! > > Best, > Max Xu > > > On Wed, Jul 27, 2022 at 2:04 PM Kai Wang > wrote: > > > Congratulations Michael! > > > > Thanks, > > Kai > > > -- BR, Qiang Huang
Re: [DISCUSS] Restart Release Pulsar 2.7.5
+1 Penghui On Jul 27, 2022, 11:00 +0800, Zixuan Liu , wrote: > +1 > > Thanks, > Zixuan > > Zike Yang 于2022年7月26日周二 22:24写道： > > > +1 > > > > Thanks > > Zike Yang > > > > On Tue, Jul 26, 2022 at 7:46 PM Hang Chen wrote: > > > > > > +1 > > > > > > Thanks, > > > Hang > > > > > > Enrico Olivelli 于2022年7月26日周二 19:21写道： > > > > > > > > +1 > > > > > > > > thank you > > > > > > > > Enrico > > > > > > > > Il giorno mar 26 lug 2022 alle ore 13:19 Haiting Jiang > > > > ha scritto: > > > > > > > > > > Hello Pulsar Community, > > > > > > > > > > Previously in early February, we had a discussion about 2.7.5 > > release in [1]. > > > > > But unfortunately, there seems to be a test regression in Candidate > > 1 and the > > > > > release process is blocked since [2]. I would like to pick up the > > work and > > > > > volunteer to be the release manager. > > > > > > > > > > Here [3] you can find the list of 52 commits to branch-2.7 since the > > 2.7.4 > > > > > release. The commits number is 41 more than RC1. Since 2.7.5 should > > be the > > > > > last release of branch 2.7, I plan to include all existing commit > > this time. > > > > > After that branch 2.7 should not accept any more commits. > > > > > > > > > > There are 4 closed PRs targeting 2.7.5 that have not yet been > > cherry-picked > > > > > [4]. I'll follow up on these PRs and solve the test regression issue > > and start > > > > > preparing branch-2.7 RC2 for the release. > > > > > > > > > > BR, > > > > > Haiting Jiang > > > > > > > > > > [1] https://lists.apache.org/thread/wxl5z67nnzv05r5vldjq3c6sm7fxnrcc > > > > > [2] https://lists.apache.org/thread/yvrmwldtzbo9lbs0jqjfj31lxtd792jq > > > > > [3] https://github.com/apache/pulsar/compare/v2.7.4...branch-2.7 > > > > > [4] > > https://github.com/apache/pulsar/pulls?q=is%3Apr+label%3Arelease%2F2.7.5+-label%3Acherry-picked%2Fbranch-2.7 > >
