Hi Pulsarers,
As we know[1], there are some issues in the current Pulsar release notes
(RN), for example:
- For Pulsar users
They cannot capture the highlights quickly since the RN is a raw dump of
PRs.
- For Pulsar release managers (RM)
They feel overwhelmed by the **manual** workload of genera
Congratulations Marvin!
On Tue, Dec 14, 2021 at 8:42 AM Guangning E wrote:
> Configrats!
>
> Thanks,
> Guangning
>
> Huanli Meng 于2021年12月14日周二 08:34写道：
>
> > Congratulations Marvin!
> >
> > BR//Huanli
> >
> > > On Dec 13, 2021, at 5:46 PM, linlin wrote:
> > >
> > > The Apache Pulsar Project M
Hi Pulsar enthusiasts,
As you may notice, there are more and more documentation contributions
nowadays, which is great!
Similar to coding style guides, in the field of technical writing, a
writing style guide is a must to improve users' experience and eliminate
writers' workload.
To improve t
nt on this PR [2], thanks.
[1] https://github.com/apache/pulsar/tree/master/.github/ISSUE_TEMPLATE
[2] https://github.com/apache/pulsar/pull/13359
On Tue, Dec 14, 2021 at 9:09 PM Yu Liu wrote:
> Spot on.
> This also reminds me that we can create custom issue forms by adding YAML
> f
Hi Enrico,
Thanks for your great effort on the 2.9.0 release.
Circling back to see if there is any progress of the 2.9.0 website updates
[1].
Currently, the 2.9.0 doc is not available on the website and the 2.9.0 doc
set has not been generated yet, any updates? Thanks
[1] https://github.com/apa
[a] https://github.com/apache/pulsar/wiki/Release-process#16-update-the-site
[b] https://pulsar.apache.org/blog/2021/09/23/Apache-Pulsar-2-8-1/
On Fri, Dec 17, 2021 at 7:36 PM Enrico Olivelli wrote:
> Il giorno ven 17 dic 2021 alle ore 09:45 Yu ha scritto:
>
> > Hi Enrico,
> &g
Hi Dave,
Thanks for your instructions.
+1 for not migrating the incubating versioned docs since they are too old
and almost no one uses them. Besides, as you suggested, we can regenerate
those docs if needed.
On Mon, Dec 20, 2021 at 11:18 AM Dave Fisher wrote:
> This is a question for the dev@
for Pulsar. Wishing you a
New Year loaded with laughter and blessed with smiles. Wishing you a New
Year that you remember all your life. Happy 2022!
Cheers,
Yu
[1]
https://docs.google.com/spreadsheets/d/1U2aYjla-oGxAHkCpdBCBy_EWNwHKOvAJ-6-3IiVrJ1U/edit#gid=1283297735
[2]
https://github.com
Kudos to Zhangjian! And thanks for your documentation contribution, welcome
to submit more commits!
On Thu, Jan 6, 2022 at 10:20 AM Haiting Jiang
wrote:
> Congrats, Zhangjian!
>
> Thanks,
> Haiting Jiang
>
> On 2022/01/06 02:05:53 Jia Zhai wrote:
> > Congratulations to Zhangjian!
> > Thanks for
Hi Pulsarers,
To move [PIP 112: Generate Release Notes Automatically] forward, we need to
define the Pulsar Release Notes Architecture, which only includes major
changes (important features/enhancements/bug fixes) in list form rather
than a raw dump of PRs.
Here [2] is the draft, feel free to com
Congratulations! And thanks for contributing docs!
On Fri, Jan 21, 2022 at 4:36 PM ZhangJian He wrote:
> Congratulations!
>
> Thanks
> ZhangJian He
>
> Enrico Olivelli 于2022年1月21日周五 15:42写道：
>
> > Congratulations!
> >
> >
> > Enrico
> >
> > Il Ven 21 Gen 2022, 08:38 Aloys Zhang ha
> scritto:
>
Hi Michael,
Thanks for raising this up.
> It is only in a Google Sheet right now, though. Maybe the owners of
the Google doc would consider contributing it to the website?
This google sheet [1] has been already contributed to our community.
Everyone has access to view and comment on it.
> The w
Hi Pulsarers,
As you may notice, the images in Pulsar documentation are in inconsistent
styles, which affect user experience. This issue may be caused by:
1) Pulsar community does not have design style guides.
2) Original images are not shared, so that contributors can not be able to
re-use the
sing GitHub. On the other hand, by
> putting it in our git repo, it would be easier for anyone to
> contribute changes without giving blanket write access to the doc. Git
> would also provide a public record of the history of the doc.
>
> > Fixed, PTAL [2]
>
> Than
Congrats, Aloys Zhang!
On Thu, Feb 10, 2022 at 7:58 PM Ruguo Yu wrote:
> Congratulations, Aloys Zhang!
>
> Thanks
>
> Ruguo Yu
>
>
>
> On 2022/02/10 02:46:11 linlin wrote:
>
> > The Apache Pulsar Project Management Committee (PMC) has invited Aloys
>
Hi Pulsarers,
As we move forward with PIP 87 [1], we’ve migrated the Pulsar website
contents to an independent repo, pulsar-site, per the agreement made by our
community [2].
This migration makes us think of the doc repo. After thinking twice, our
recommendation is to **keep the Pulsar doc repo a
Bumping up this thread, any thoughts? Thanks
On Fri, Jan 28, 2022 at 1:00 AM Yu wrote:
> Hi Pulsarers,
>
>
> As you may notice, the images in Pulsar documentation are in inconsistent
> styles, which affect user experience. This issue may be caused by:
>
> 1) Pulsar co
&km_CPC_Device=c&km_CPC_placement=&km_CPC_target=
On Tue, Feb 15, 2022 at 8:17 PM Enrico Olivelli wrote:
> Yu,
>
> Il Mar 15 Feb 2022, 13:12 Yu ha scritto:
>
>> Bumping up this thread, any thoughts? Thanks
>>
>> On Fri, Jan 28, 2022 at 1:00
Hi Pulsarers,
Since there is no discussion and objection, we'll keep the doc repo stay in
the pulsar repo and continue to move forward with PIP 87.
Hi Lili,
Congrats! Well deserved! You've made a lot of great changes to the Pulsar
website!
On Tue, Feb 15, 2022 at 5:56 PM ZhangJian He wrote:
> Congratulations
>
> Thanks
> ZhangJian He
>
> Huanli Meng 于2022年2月15日周二 17:03写道：
>
> > Congratulations Li.
> >
> > BR// Huanli
> >
> > > On Feb 15,
Hi Pulsarers,
As you may notice, the new Pulsar website goes live!
https://pulsar.apache.org/
We hope you enjoy the new feature and the fresh appearance!
CHANGE: documentation main page URL is changed from
https://pulsar.apache.org/docs/en/next/standalone/ to
https://pulsar.apache.org/docs/next/
at 11:52 AM Dianjin Wang
wrote:
> Great work!
>
> Any plans for multi-language translation support? There were some languages
> supported, such as Chinese, Japanese, French and more, but now cannot find
> the button in the new website.
>
> Best,
> Dianjin Wang
>
>
>
2], thanks.
[1] https://github.com/apache/pulsar/pull/14344
[2]
https://docs.google.com/document/d/1IV35SI_F8G8cL-Vuzknc6RTGLK9_edRMpZpnrHvAWNs/edit#bookmark=id.86uprmy9cv2w
On Thu, Feb 17, 2022 at 12:42 PM Sijie Guo wrote:
> Hi Yu,
>
> Thank you and all the other contributors for all t
gt;
> On Thu, Feb 17, 2022 at 8:33 AM Sijie Guo wrote:
>
> > Remove users@
> >
> > Yu - I have received quite a few questions about broken links.
> >
> > https://pulsar.apache.org/docs/en/security-jwt/ <- This is broken.
> >
> > It seems to be me
gt; Maybe you can open a INFRA ticket on ASF jira
>
>
> Enrico
>
>
> Il Mer 16 Feb 2022, 04:23 Yu ha scritto:
>
>> Hi Enrico, do you mean the price of LucidChart? Here it is:
>>
>> [image: image.png]
>>
>>
>> https://lucid.app/pricing/lucidch
Hi Michael,
Thanks for your contribution!
1 "Security Policy and Supported Versions" is shown on the Pulsar website
[1]
1.1 It is in "master" (site2/docs) rather than a versioned section.
1.2 Some contents are not shown correctly. It is strongly recommended that
RUN A LOCAL PREVIEW BEFORE SUBMITT
Hi Pulsarers,
For Pulsar release notes [1], we had issues below for a long time.
- All contents are on a single Pulsar release note page. No navigations.
It's easy to get lost and hard to understand which changes belong to which
Pulsar version.
- Java, C++, Python, WebSocket clients do not have i
;
> >> 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
> >>
> >> On Fri, Mar 4, 2022 at 2:59 AM Yu li...@apache.org>> wrote:
> >> Hi Pulsare
Hi penghui,
> 1. The title of the PR should be refined during the PR review, before
merging it.
For this item, I'll define the writing rules for PR titles and send them
out for review.
On Tue, Mar 8, 2022 at 10:00 AM PengHui Li wrote:
> For 2.10.0 release, I'm using `gh` command to generate t
Dear Pulsar female contributors,
Success doesn’t come easy and women never give up. Thanks for bringing so
much love and support to the Pulsar community. And every man needs a woman
when his life is a mess, just like the game of chess — the queen protects
the king. Best wishes on International Wom
> 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
>
Congrats Andrey!
On Mon, Mar 14, 2022 at 9:15 AM Hang Chen wrote:
> Congratulations Andrey!
>
> Best,
> Hang
>
> Li Li 于2022年3月14日周一 08:41写道：
> >
> > Congrats Andrey!
> >
> > -Li Li
> >
> > > On Mar 11, 2022, at 5:54 PM, PengHui Li wrote:
> > >
> > > Congrats Andrey!
> > >
> > > -Penghui
> > >
Hi Pulsarers,
We submit or review PRs almost every day, we might see many vague and
unclear PR titles that decrease team efficiency and productivity.
Good PR titles offer bring many benefits, such as speeding up the review
process and improving search efficiency.
To solve the vague PR title issu
at 9:10 PM Enrico Olivelli wrote:
> Thank you Yu,
> I left some feedback on the gdoc
>
> Overall it is a great proposal.
>
> It will probably be hard to enforce, we will have to spend time and
> fix the title when we see the wrong title.
> but I totally agree with you, t
eline before merging it.
>
> It's not easy to reach a consensus very fast,
> but we can finally reach it :)
>
> Thanks,
> Penghui
>
> On Fri, Mar 18, 2022 at 2:47 PM Yu wrote:
>
> > Thanks for your suggestions, Penghui, Enrico, and Nicoló Boschi.
> >
bout the "Limit the subject
> line to 50 characters" rule in Chris Beam's awesome "How to Write a Git
> Commit Message" blog post: https://cbea.ms/git-commit/#limit-50
>
> Do we care about the general rule that a git commit message should be
> limited to 50
For example, GitHub's UI suggests to write commit messages that are less
> than 50 characters. There's more explanation about the "Limit the subject
> line to 50 characters" rule in Chris Beam's awesome "How to Write a Git
> Commit Message" blog post: https
difficulties with the link,
do not hesitate to contact me by email.
Let’s continue working together to build an awesome Pulsar community. Thank
you!
Cheers,
Yu
://forms.office.com/r/2NmBaS5yW6
Thank you! :-D
Cheers,
Yu
On Mon, Mar 28, 2022 at 11:25 AM Yu wrote:
> Hi Everyone,
>
> Have you checked out the new Pulsar website (
> https://pulsar-next.staged.apache.org/)?
>
> It’s been 30 days since the website beta started and we’re eager
take the
results from the survey seriously, as they help shape important decisions
on the Pulsar website.
Start the English survey NOW: https://forms.office.com/r/QK6FYdQ158
OR
Start the Chinese survey NOW: https://forms.office.com/r/2NmBaS5yW6
Thanks!
Cheers,
Yu
On Thu, Mar 31, 2022 at 4:40
Congrats Zike! Well deserved!
On Wed, Apr 13, 2022 at 7:00 PM Enrico Olivelli wrote:
> Congratulations
>
> Enrico
>
> Il Mer 13 Apr 2022, 12:38 Hang Chen ha scritto:
>
> > Congrats Zike!
> >
> > Best,
> > Hang
> >
> > Haiting Jiang 于2022年4月13日周三 18:16写道：
> > >
> > > Congrats!
> > >
> > > Thank
Congrats Zhangmin!
On Wed, Apr 13, 2022 at 6:59 PM Enrico Olivelli wrote:
> Congratulations
>
> Enrico
>
> Il Mer 13 Apr 2022, 12:39 Hang Chen ha scritto:
>
> > Congrats Zhangmin!
> >
> > Best,
> > Hang
> >
> > Haiting Jiang 于2022年4月13日周三 18:16写道：
> >
> > >
> > > Congrats!
> > >
> > > Thanks,
The Apache Pulsar Project Management Committee (PMC) has invited Ruguo Yu (
https://github.com/yuruguo) to become a committer and we are pleased to
announce that he has accepted.
Welcome and Congratulations, Ruguo Yu!
Please join us in congratulating and welcoming Ruguo Yu onboard!
Best Regards
Hi Pulsarers,
For the Ecosystem Page [1], we want to make it a place for the Pulsar
community to come together and share the components the community needs to
build better streaming data pipelines and event-driven applications.
So I've collected all Pulsar-related plugins and tried to re-catego
-connect-plugin
Anonymitaet
On Wed, Apr 20, 2022 at 2:08 AM Chris Bartholomew <
chris.bartholo...@kesque.com> wrote:
> Hi Anonymitaet,
>
> I provided input on the "Components Managed by DataStax" as a comment in
> the Google doc. If you need any more information, pl
nd the C client, but we don't call that a client
> wrapper, is called the Python client.
>
> On 2, I agree it makes sense to call it a "Security Plugin".
>
> Thanks,
> Chris
>
> On Wed, 20 Apr 2022 at 01:06, Yu wrote:
>
>> Hi Chris,
>>
>
Hi Pulsarers,
Recently, we've found that many open source communities use GitHub
Discussions to facilitate effective communication, such as users can ask
questions, share ideas, and build connections with each other easily [1].
GitHub Discussions is designed to:
- Provide centralized community s
velopment
> activities to commits@.
>
> Best,
> tison.
>
>
> Niclas Hedhman 于2022年4月21日周四 20:16写道：
>
>>
>> If/when GitHub disappears, will the community suffer from missing
>> information? If so, need to solve the "back to ASF"-path, so it isn
channel is Slack is taking a final look at the
> > ecosystem and docs pages. We will soon have a launch date to share.
> >
> > Thanks to all who provided input via the survey Yu shared a few weeks
> ago.
> > (1) Note: There was a Docusaurus update that caused breaking changes
>
ww.apache.org/foundation/voting.html
On Fri, Apr 22, 2022 at 11:00 PM Dave Fisher wrote:
> Hi Yu,
>
> > On Apr 21, 2022, at 11:46 PM, Yu wrote:
> >
> > Thanks all!
> >
> > I understand that we need to follow the Apache way (If it didn’t happen
> on
> > th
Thanks Penghui and Dianjin.
Lili and I will submit applications to improve our user experience on the
Pulsar website and documentation. We aim to fix some of these issues [1].
Feel free to comment if you have more suggestions on that, thanks!
[1]
https://github.com/apache/pulsar/issues?q=is%3Aope
Congrats Nicolò!
On Wed, Apr 27, 2022 at 7:48 AM PengHui Li wrote:
> The Apache Pulsar Project Management Committee (PMC) has invited Nicolò
> Boschi
> https://github.com/nicoloboschi to become a committer and we are pleased
> to
> announce that he has accepted.
>
> Welcome and Congratulations,
achieve expected outcomes.
- For the student: acquire new skills and level up your developer portfolio.
# Project Mentor
Yu Liu
# Your Email
li...@apache.org
y...@streamnative.io
# Your Apache ID
liuyu
Chinese version
# 项目名称
> Item 2: Implement the message chunking feature at the go client and
> push the PR out
> Item 3: Add unit tests to verify it
> Item 4: Add the documentation for this feature
> …
> Project Mentor: Zike Yang
> Your Name: Zike Yang
> Your Email:
> Your Apache ID:
>
>
[1] https://lists.apache.org/thread/xjccxbozlw7jqlldm2dw0yc74cydknvd
Yu and Lili
> > Max Xu
> >
> >
> >
> > On Thu, May 12, 2022 at 1:24 AM Aaron Williams wrote:
> >
> > > Looks great! Thank you
> > >
> > >
> > > On Wed, May 11, 2022 at 10:19 AM Chris Latimer >
> > > wrote:
&g
Hi everyone,
For the new Pulsar website, we got much negative feedback about the
blue background
color, it decreases readability significantly.
They prefer the white background color as before, which looks more clearly.
Feel free to thumb up on this comment [1] if you feel the same.
We may cha
. Also, I’ve been trying google as an
> alternative to our broken search and it is giving me ancient docs instead
> of latest.
> >
> > IMO - These graphical issues are comparatively trivial. That and there
> was a survey. Why weren’t these criticisms provided?
> >
>
/C02Q4JLUB38/p1652425677759509?thread_ts=1649233950.692869&cid=C02Q4JLUB38
[2] https://support.google.com/analytics/answer/11583528
Yu and Lili
On Sat, May 14, 2022 at 4:01 AM Dave Fisher wrote:
> Hi Yu -
>
> Google Analytics are no longer allowed on ASF websites due to privacy
> con
docs.google.com/document/d/12De2btkDHQVaqUlHjTqERmroMLKGhHdiC7rEttFTyqc/edit#heading=h.wu6ygjne8e35
[2]
https://docs.google.com/document/d/1wszdtMRo6MhKbVaggPK7_bnKaC4TewuT--GWZZxJNGg/edit#
Yu and Lili
/1bQfZkSu5nG1tNycpmXXtUFn-Z5-h-uqHv6IXsCEySQ8/edit
[2] https://github.com/harupy/auto-labeling
[3] https://github.com/apache/pulsar/issues/15797
[4] https://github.com/apache/pulsar-test-infra/tree/master/doc-label-check
[5] https://github.com/maxsxu/action-labeler
Yu and Max
Hi Dezhi, kudos to you! Well deserved!
On Wed, Jun 8, 2022 at 9:52 AM Li Li wrote:
> Congratulations Dezhi!
>
> Thanks,
> Li Li
>
> > On Jun 7, 2022, at 9:13 PM, PengHui Li wrote:
> >
> > Congratulations Dezhi!
> >
> > Penghui
> > On Jun 7, 2022, 17:22 +0800, Enrico Olivelli ,
> wrote:
> >> Co
e.com/document/d/1Qw7LHQdXWBW9t2-r-A7QdFDBwmZh6ytB4guwMoXHqc0/edit#
[5]
https://docs.google.com/document/d/1d8Pw6ZbWk-_pCKdOmdvx9rnhPiyuxwq60_TrD68d7BA/edit#heading=h.wu6ygjne8e35
[6]
https://docs.google.com/document/d/16Hp7Sc86MQtL0m8fc2w_TrcKXAuglwRwHmdmwfk00mI/edit#heading=h.b8ogodj5sj0
Yu
oject-managed resources once they are
"more" finalized.
[1] https://pulsar.apache.org/contributing/
[2] https://github.com/apache/pulsar#documentation-1
On Tue, Jun 14, 2022 at 1:23 PM Michael Marshall
wrote:
> Hi Yu,
>
> Thank you for your efforts to improve our documentation.
+1 for enabling the GitHub Discussion as I proposed before.
At that time, the main concern was not able to sync info between GitHub
Discussion and Mailing List. Since the concern can be resolved now, we can
make the most of GitHub Discussion as it's a powerful supplementary to
community collaborat
n and relationship between the puslar/site2 repo [2]
and puslar-site/site2 repo [3].
[1]
https://docs.google.com/document/d/1-1uJyd1k9_h56xiiVRVOnrLcCnTmg9n7SrHhNVNEEi4/edit#
[2] https://github.com/apache/pulsar/tree/master/site2
[3] https://github.com/apache/pulsar-site/tree/main/site2
Yu and Lili
On Thu, J
thub.com/apache/pulsar-site/blob/7441570e2a79c56f073bdc8c3dabe41fbad7411a/site2/website-next/data/team.js#L29
[6] https://spark.apache.org/committers.html
Yu and Wenqing
e.org/release-notes/
[2]
https://github.com/apache/pulsar/wiki/Release-process#16-write-release-notes
Yu & urfree
your change since we've already submitted a fix [1].
> If we don't find a quick solution, I'll push a revert to unblock the
master branch.
Feel free to comment, thank you!
[1] https://github.com/apache/pulsar/pull/16437
Yu and Max
On Thu, Jul 7, 2022 at 12:06 PM Michael Marshall
submission process. This should enable better productivity.
Welcome and congratulations, Zixuan Liu!
Please join us in congratulating and welcoming Zixuan Liu onboard!
Best Regards,
Yu on behalf of the Pulsar PMC
Hi team,
Now we have a fresh "Community" page [1], which shows the Pulsar PMC list,
contributors over time, monthly active contributors, etc.
Thanks Wenqing for making this happen!
[1] https://pulsar.apache.org/community#section-community
Yu
On Tue, Jul 5, 2022 at 9:15 PM Yu wr
Hi tison, thanks for creating this vote!
I thought we reached a lay consensus since there was no objection since the
last discussion [1]
+1 for this proposal.
I've explained the reasons and showed the benefits previously [2]
[1] https://lists.apache.org/thread/1y7zbchlbokwnpd0jv2tt5jtzg6px6yn
[2]
to be part of the great event! Save your spot today!
Best,
Yu
[1] https://pulsar-summit.org/event/san-francisco-2022
Congrats Michael! Thanks for your contribution to the doc and website!
On Wed, Jul 27, 2022 at 12:46 AM Nicolò Boschi wrote:
> Congrats! Very well deserved!!
>
> Nicolò Boschi
>
> Il Mar 26 Lug 2022, 18:26 Christophe Bornet ha
> scritto:
>
> > Congratulations Michael ! Well deserved !
> >
> > L
+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/
Hi Zixuan and Tison,
Thanks for your comments!
We're considering your suggestion and will turn the proposal into a PIP and
call a vote.
Yu, Max, mangoGoForward
On Mon, Aug 1, 2022 at 4:29 PM Zixuan Liu wrote:
> Hi Yu,
>
> This is a good idea, I noticed this thread for a long tim
other thoughts
Feel free to comment, thank you!
[1] https://lists.apache.org/thread/sk9ops3t94jmzc5tndk08y9khf7pj6so
[2] https://github.com/apache/pulsar/pulls
[3]
https://docs.google.com/document/d/1sJlUNAHnYAbvu9UtEgCrn_oVTnVc1M5nHC19x1bFab4/edit?pli=1#
Yu, Max, mangoGoForward
, @laminar*, @*danpi
[1] https://pulsar.apache.org/tools/pulsar-admin/2.11.0-SNAPSHOT/#functions
[2]
https://docs.google.com/spreadsheets/d/1YHYTkIXR8-Ql103u-IMI18TXLlGStK8uJjDsOOA0T20/edit#gid=1784579914
[3] https://github.com/apache/pulsar/pull/16853
Yu
ed based on Angular) [2],
seems that Angular only saves one char.
For example,
- Angular: feat(broker): add xxx → (): occupy 3 chars
- Ours: [feat][broker] add xxx → (): occupy 4 chars
(2) I agree with Michael. Brackets make info clearer.
Yu
[1]
https://github.com/apache/pulsar/pull/16836
to issue 2.
[1]
https://github.com/angular/angular/blob/main/CONTRIBUTING.md#commit-message-header
[2]
https://docs.google.com/document/d/1d8Pw6ZbWk-_pCKdOmdvx9rnhPiyuxwq60_TrD68d7BA/edit?pli=1#bookmark=id.y8943h392zno
Yu
On Wed, Aug 10, 2022 at 6:05 PM Yu wrote:
> Hi Lari,
>
> Tha
s://docs.google.com/document/d/1d8Pw6ZbWk-_pCKdOmdvx9rnhPiyuxwq60_TrD68d7BA/edit?pli=1#bookmark=id.y8943h392zno
[3] https://github.com/apache/pulsar/pulls
On Wed, Aug 10, 2022 at 6:11 PM Yu wrote:
>
> Hi team,
>
> Thanks for all your suggestions!
>
> I'll move PIP 19
Hi team, Thanks for all your suggestions! I'll move PIP 198 forward since
we get 3 binding votes (Penghui, Lari, Michael) [1].
[1] https://lists.apache.org/thread/m7hfgpdjthrk8ogz3mnkprs018tkkc0m
Yu
!
[1]
https://docs.google.com/document/d/1sJlUNAHnYAbvu9UtEgCrn_oVTnVc1M5nHC19x1bFab4/edit?pli=1
[2]
https://github.com/angular/angular/blob/main/CONTRIBUTING.md#commit-message-header
[3]
https://docs.google.com/document/d/1d8Pw6ZbWk-_pCKdOmdvx9rnhPiyuxwq60_TrD68d7BA/edit?pli=1#bookmark=id.y8943h392zno
[4] https:/
.
I'll initiate an official discussion on these details and the definition of
[type][scope] in another independent email.
[1]
https://docs.google.com/document/d/1d8Pw6ZbWk-_pCKdOmdvx9rnhPiyuxwq60_TrD68d7BA/edit?pli=1#bookmark=id.y8943h392zno
Yu and mangoGoForward
On Mon, Aug 15, 2022 at 12:
Hi team,
Feel free to choose your desired convention **before EOD 8/16 (UTC +8)**.
We'll close this discussion and move to the next topic after that time.
Thank you!
Yu and mangoGoForward
On Mon, Aug 15, 2022 at 6:27 PM Yu wrote:
> Hi tison,
>
> Thanks for your suggesti
31kmgr65fj0nfnn
[3]
https://docs.google.com/document/d/1d8Pw6ZbWk-_pCKdOmdvx9rnhPiyuxwq60_TrD68d7BA/edit?pli=1#bookmark=id.y8943h392zno
[4]
https://docs.google.com/document/d/1d8Pw6ZbWk-_pCKdOmdvx9rnhPiyuxwq60_TrD68d7BA/edit?pli=1#bookmark=kix.849jztd92uk7
Yu
/pulsar.apache.org/docs/next/client-libraries-rest
[3]
https://docs.google.com/document/d/1d8Pw6ZbWk-_pCKdOmdvx9rnhPiyuxwq60_TrD68d7BA/edit?pli=1#bookmark=id.nnekhkthmwlh
Yu
On Thu, Aug 18, 2022 at 10:50 AM Zixuan Liu wrote:
> Thank yu for your work! Overall looks good to me, but I would
/tools/pulsar-config/2.11.0-SNAPSHOT/#/
Yu, signormercurio, urfreespace
Congrats Jiwei!
On Fri, Aug 19, 2022 at 10:45 AM Zixuan Liu wrote:
> Congrats!
>
> Zixuan
>
> Jun M 于2022年8月19日周五 10:16写道：
>
> > Congrats to Jiwei!
> >
> >
> > Cheers,
> > Jun
> >
>
om/apache/pulsar/pull/16055
- Add guides:
[feat][workflow] Add instructions for previewing website changes,
https://github.com/apache/pulsar-site/pull/136
~~
Yu
On Thu, Aug 18, 2022 at 11:51 PM Zixuan Liu wrote:
> > Since here uses a singular noun, how about using "dep"
oth “storage” and “tiered storage” scopes.
Bookie changes go to “storage”.
Tiered storage changes go to “tiesto” (abbr. "ts" is not used since it
might be confused with TypeScript).
Hi developers, which do you prefer? Or any other suggestions? Thank you!
Yu
On Fri, Aug 19, 2022 at 5:01
nsidered to replace it.
[1] https://github.com/apache/pulsar/issues/15664
Yu and signormercurio
On Thu, Aug 18, 2022 at 9:46 PM Dave Fisher wrote:
>
>
> Sent from my iPhone
>
> > On Aug 18, 2022, at 4:55 AM, Yu wrote:
> >
> > Hi team,
> >
> > To red
-1uJyd1k9_h56xiiVRVOnrLcCnTmg9n7SrHhNVNEEi4/edit#bookmark=id.q5m2r5pimdi6
[2] https://github.com/apache/pulsar/issues/16637
Yu
rmats are fine to go:
- Submit breaking changes
[feat][broker]! Support xx
- Submit PIP changes
[feat][broker] PIP-198: Support xx
Feel free to comment, thank you!
[1] https://pulsar.apache.org/docs/next/admin-api-packages
Yu and Zi
d8Pw6ZbWk-_pCKdOmdvx9rnhPiyuxwq60_TrD68d7BA/edit?pli=1#bookmark=id.khz275ok35u5
[2]
https://docs.google.com/document/d/1d8Pw6ZbWk-_pCKdOmdvx9rnhPiyuxwq60_TrD68d7BA/edit?pli=1#bookmark=id.nnekhkthmwlh
Yu and Zixuan
On Mon, Aug 22, 2022 at 12:40 PM Yu wrote:
> Thank you tison and Zixuan!
>
> Agre
quot;misc" or "chore"? [1]
Choice A: misc
Choice B: chore
Thank you all!
[1]
https://docs.google.com/document/d/1d8Pw6ZbWk-_pCKdOmdvx9rnhPiyuxwq60_TrD68d7BA/edit?pli=1#bookmark=id.58q1qxhu7pio
Yu
On Mon, Aug 22, 2022 at 12:44 PM Yu wrote:
> Hi
Hi Jiuming, Yunze, tison,
Thanks for your vote!
Hi tison,
> "packaging logics"
> For example, build the docker image, build & publish shell scripts.
If you refer to these changes, they belong to [build] scope.
Yu and Zixuan
On Tue, Aug 23, 2022 at 1:25 PM
[1] https://lists.apache.org/thread/90rcjf1dv0fbkb5hm31kmgr65fj0nfnn
[2]
https://docs.google.com/document/d/1d8Pw6ZbWk-_pCKdOmdvx9rnhPiyuxwq60_TrD68d7BA/edit?pli=1#bookmark=id.y8943h392zno
Yu and mangoGoForward
On Tue, Aug 23, 2022 at 5:59 PM Yu wrote:
> Hi Jiuming, Yunze, tison,
Hi team,
Now is 3 working days after the initial discussion
We'll start replacing brodocs with docsify for docs since there is no
objection or technical suggestions.
Yu, signormercurio, urfreespace
On Fri, Aug 19, 2022 at 5:09 PM Yu wrote:
> Thanks Dave!
>
> > How is this se
e "PIP
metadata" file.
3. ...
Yu
On Wed, Aug 24, 2022 at 10:01 AM PengHui Li wrote:
> Hi Rajan,
>
> > I didn't understand this part. You want one to create a PR before
> submitting a proposal? That's clearly not a good idea because if the PIP
> approach wi
1 - 100 of 222 matches
Mail list logo
