[
https://issues.apache.org/jira/browse/FLINK-31704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17707954#comment-17707954
]
Weijie Guo commented on FLINK-31704:
------------------------------------
[~dannycranmer], Introduce a new branch is indeed a feasible way. But I want to
share another idea.
I had an offline discussion with [~renqs], and the conclusion is that for
external connectors, Flink's documentation seems to track a stable branch, but
not a released tag. The advantage of this approach is that users can see our
improvements and fixes to the document timely. At the same time, since we are
based on a stable branch that already has a release version and will not
introduce new features, there are no problems like this ticket. WDYT?
> Pulsar docs should be pulled from dedicated branch
> --------------------------------------------------
>
> Key: FLINK-31704
> URL: https://issues.apache.org/jira/browse/FLINK-31704
> Project: Flink
> Issue Type: Technical Debt
> Components: Connectors / Pulsar, Documentation
> Reporter: Danny Cranmer
> Priority: Major
>
> Pulsar docs are pulled from the {{main}}
> [branch|https://github.com/apache/flink/blob/release-1.17/docs/setup_docs.sh#L49].
> This is dangerous for final versions since we may include features in the
> docs that are not supported. Update Pulsar to pull from a dedicated branch or
> tag.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
