You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Danny Cranmer (Jira)" <ji...@apache.org> on 2023/04/15 16:43:00 UTC

[jira] [Commented] (FLINK-31779) Track stable branch of externalized connector instead of specific release tag

    [ https://issues.apache.org/jira/browse/FLINK-31779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17712683#comment-17712683 ] 

Danny Cranmer commented on FLINK-31779:
---------------------------------------

[~Weijie Guo] can you open a PR for 1.16/1.17 branches too please?

> Track stable branch of externalized connector instead of specific release tag
> -----------------------------------------------------------------------------
>
>                 Key: FLINK-31779
>                 URL: https://issues.apache.org/jira/browse/FLINK-31779
>             Project: Flink
>          Issue Type: Improvement
>          Components: Connectors / Common, Documentation
>            Reporter: Weijie Guo
>            Assignee: Weijie Guo
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.18.0
>
>
> As we [discussed|https://github.com/apache/flink-connector-opensearch/pull/17], docs for externalized connectors should point to the branch where that version of the docs are published, otherwise documentation fixes are not visible until a new release is made. After this, we can safely delete all dedicated doc branches.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)