Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[website][upgrade] fix: resolve compatibilities for docs migration of version next/2.8.0/2.7.3 #12415

Merged
merged 18 commits into from
Oct 22, 2021

Conversation

urfreespace
Copy link
Member

Master Issue: #11766

Motivation

website upgrade

Modifications

Click to Preview

Verifying this change

  • Make sure that the change passes the CI checks.

(Please pick either of the following options)

This change is a trivial rework / code cleanup without any test coverage.

(or)

This change is already covered by existing tests, such as (please describe tests).

(or)

This change added tests and can be verified as follows:

(example:)

  • Added integration tests for end-to-end deployment with large payloads (10MB)
  • Extended integration test for recovery after broker failure

Does this pull request potentially affect one of the following parts:

If yes was chosen, please highlight the changes

  • Dependencies (does it add or upgrade a dependency): (yes / no)
  • The public API: (yes / no)
  • The schema: (yes / no / don't know)
  • The default values of configurations: (yes / no)
  • The wire protocol: (yes / no)
  • The rest endpoints: (yes / no)
  • The admin cli options: (yes / no)
  • Anything that affects deployment: (yes / no / don't know)

Documentation

For contributor

For this PR, do we need to update docs?

  • If yes, please update docs or create a follow-up issue if you need help.

  • If no, please explain why.

For committer

For this PR, do we need to update docs?

  • If yes,

    • if you update docs in this PR, label this PR with the doc label.

    • if you plan to update docs later, label this PR with the doc-required label.

    • if you need help on updating docs, create a follow-up issue with the doc-required label.

  • If no, label this PR with the no-need-doc label and explain why.

Signed-off-by: LiLi <urfreespace@gmail.com>
Signed-off-by: LiLi <urfreespace@gmail.com>
Signed-off-by: LiLi <urfreespace@gmail.com>
Signed-off-by: LiLi <urfreespace@gmail.com>
Signed-off-by: LiLi <urfreespace@gmail.com>
Signed-off-by: LiLi <urfreespace@gmail.com>
Signed-off-by: LiLi <urfreespace@gmail.com>
Signed-off-by: LiLi <urfreespace@gmail.com>
@eolivelli
Copy link
Contributor

@urfreespace:Thanks for your contribution. For this PR, do we need to update docs?
(The PR template contains info about doc, which helps others know more about the changes. Can you provide doc-related info in this and future PR descriptions? Thanks)

@urfreespace
Copy link
Member Author

@Anonymitaet @tuteng PTAL, thanks.

@Anonymitaet Anonymitaet added doc Your PR contains doc changes, no matter whether the changes are in markdown or code files. and removed doc-label-missing labels Oct 19, 2021
@Anonymitaet
Copy link
Member

@Anonymitaet
Copy link
Member

I've finished the review, PTAL, thanks.

Signed-off-by: LiLi <urfreespace@gmail.com>
Signed-off-by: LiLi <urfreespace@gmail.com>
Signed-off-by: LiLi <urfreespace@gmail.com>
Signed-off-by: LiLi <urfreespace@gmail.com>
Signed-off-by: LiLi <urfreespace@gmail.com>
Signed-off-by: LiLi <urfreespace@gmail.com>
@urfreespace
Copy link
Member Author

@Anonymitaet all resolved, PTAL, thanks.

Signed-off-by: LiLi <urfreespace@gmail.com>
Signed-off-by: LiLi <urfreespace@gmail.com>
Signed-off-by: LiLi <urfreespace@gmail.com>
@Anonymitaet Anonymitaet self-requested a review October 22, 2021 07:44
@Anonymitaet Anonymitaet requested a review from tuteng October 22, 2021 07:44
@Anonymitaet Anonymitaet added this to the 2.10.0 milestone Oct 22, 2021
@Anonymitaet Anonymitaet merged commit f1dc5be into apache:master Oct 22, 2021
eolivelli pushed a commit to eolivelli/pulsar that referenced this pull request Nov 29, 2021
… version next/2.8.0/2.7.3 (apache#12415)

* feat: docs fix for 2.8.0

Signed-off-by: LiLi <urfreespace@gmail.com>

* feat: docs fix for 2.7.3

Signed-off-by: LiLi <urfreespace@gmail.com>

* feat: docs fix for next version

Signed-off-by: LiLi <urfreespace@gmail.com>

* update

Signed-off-by: LiLi <urfreespace@gmail.com>

* patch

Signed-off-by: LiLi <urfreespace@gmail.com>

* upgrade dependencies

Signed-off-by: LiLi <urfreespace@gmail.com>

* update

Signed-off-by: LiLi <urfreespace@gmail.com>

* update

Signed-off-by: LiLi <urfreespace@gmail.com>

* update

Signed-off-by: LiLi <urfreespace@gmail.com>

* update

Signed-off-by: LiLi <urfreespace@gmail.com>

* update

Signed-off-by: LiLi <urfreespace@gmail.com>

* update

Signed-off-by: LiLi <urfreespace@gmail.com>

* update

Signed-off-by: LiLi <urfreespace@gmail.com>

* update

Signed-off-by: LiLi <urfreespace@gmail.com>

* update

Signed-off-by: LiLi <urfreespace@gmail.com>

* update

Signed-off-by: LiLi <urfreespace@gmail.com>

* update

Signed-off-by: LiLi <urfreespace@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
doc Your PR contains doc changes, no matter whether the changes are in markdown or code files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants