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

KAFKA-3959: Follow-up; move upgrade notes to 0.10.3 upgrade section. #2484

Closed
wants to merge 1 commit into from

Conversation

ewencp
Copy link
Contributor

@ewencp ewencp commented Feb 2, 2017

No description provided.

@asfbot
Copy link

asfbot commented Feb 2, 2017

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/kafka-pr-jdk7-scala2.10/1422/
Test FAILed (JDK 7 and Scala 2.10).

@asfbot
Copy link

asfbot commented Feb 2, 2017

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/kafka-pr-jdk8-scala2.12/1422/
Test FAILed (JDK 8 and Scala 2.12).

@asfbot
Copy link

asfbot commented Feb 2, 2017

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/kafka-pr-jdk8-scala2.11/1425/
Test FAILed (JDK 8 and Scala 2.11).

@ijuma
Copy link
Contributor

ijuma commented Feb 2, 2017

Is it intentional that there's no entry for upgrading to 0.10.2 any more? Seems a bit odd given that there is still one for upgrading to 0.10.1.

@ewencp
Copy link
Contributor Author

ewencp commented Feb 2, 2017

Hmm, fair point, I missed that the old ones were preserved farther down. Is there a reason we're preserving all the old upgrade docs? It's just going to continue to grow indefinitely... Given that we have links to the old docs, is there any point to keeping any of the old ones around?

@ijuma
Copy link
Contributor

ijuma commented Feb 2, 2017

It's a good question. I am not sure. We could potentially just add a link to the previous version to make it convenient?

@ijuma
Copy link
Contributor

ijuma commented Feb 28, 2017

This got fixed via a different PR, which still kept the old pattern of including upgrade instructions for multiple versions though.

@asfbot
Copy link

asfbot commented Feb 28, 2017

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/kafka-pr-jdk8-scala2.11/1877/
Test PASSed (JDK 8 and Scala 2.11).

@asfbot
Copy link

asfbot commented Feb 28, 2017

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/kafka-pr-jdk8-scala2.12/1875/
Test PASSed (JDK 8 and Scala 2.12).

@asfbot
Copy link

asfbot commented Feb 28, 2017

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/kafka-pr-jdk7-scala2.10/1874/
Test PASSed (JDK 7 and Scala 2.10).

@ewencp ewencp closed this Feb 28, 2017
@sa-mao
Copy link

sa-mao commented Feb 21, 2018

I still have the same issue with other topics. that get created immediately after Kafka is started.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants