[jira] [Created] (FLINK-35683) CLONE - Verify that no exclusions were erroneously added to the japicmp plugin
Weijie Guo created FLINK-35683:
--
Summary: CLONE - Verify that no exclusions were erroneously added
to the japicmp plugin
Key: FLINK-35683
URL: https://issues.apache.org/jira/browse/FLINK-35683
Project: Flink
Issue Type: Sub-task
Reporter: Weijie Guo
Verify that no exclusions were erroneously added to the japicmp plugin that
break compatibility guarantees. Check the exclusions for the
japicmp-maven-plugin in the root pom (see
[apache/flink:pom.xml:2175ff|https://github.com/apache/flink/blob/3856c49af77601cf7943a5072d8c932279ce46b4/pom.xml#L2175]
for exclusions that:
* For minor releases: break source compatibility for {{@Public}} APIs
* For patch releases: break source/binary compatibility for
{{@Public}}/{{@PublicEvolving}} APIs
Any such exclusion must be properly justified, in advance.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (FLINK-35678) CLONE - Review and update documentation
Weijie Guo created FLINK-35678:
--
Summary: CLONE - Review and update documentation
Key: FLINK-35678
URL: https://issues.apache.org/jira/browse/FLINK-35678
Project: Flink
Issue Type: Sub-task
Affects Versions: 1.19.0
Reporter: Weijie Guo
Fix For: 1.19.0
There are a few pages in the documentation that need to be reviewed and updated
for each release.
* Ensure that there exists a release notes page for each non-bugfix release
(e.g., 1.5.0) in {{{}./docs/release-notes/{}}}, that it is up-to-date, and
linked from the start page of the documentation.
* Upgrading Applications and Flink Versions:
[https://ci.apache.org/projects/flink/flink-docs-master/ops/upgrading.html]
* ...
h3. Expectations
* Update upgrade compatibility table
([apache-flink:./docs/content/docs/ops/upgrading.md|https://github.com/apache/flink/blob/master/docs/content/docs/ops/upgrading.md#compatibility-table]
and
[apache-flink:./docs/content.zh/docs/ops/upgrading.md|https://github.com/apache/flink/blob/master/docs/content.zh/docs/ops/upgrading.md#compatibility-table]).
* Update [Release Overview in
Confluence|https://cwiki.apache.org/confluence/display/FLINK/Release+Management+and+Feature+Plan]
* (minor only) The documentation for the new major release is visible under
[https://nightlies.apache.org/flink/flink-docs-release-$SHORT_RELEASE_VERSION]
(after at least one [doc
build|https://github.com/apache/flink/actions/workflows/docs.yml] succeeded).
* (minor only) The documentation for the new major release does not contain
"-SNAPSHOT" in its version title, and all links refer to the corresponding
version docs instead of {{{}master{}}}.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (FLINK-35679) CLONE - Cross team testing
Weijie Guo created FLINK-35679:
--
Summary: CLONE - Cross team testing
Key: FLINK-35679
URL: https://issues.apache.org/jira/browse/FLINK-35679
Project: Flink
Issue Type: Sub-task
Reporter: Weijie Guo
Assignee: lincoln lee
For user facing features that go into the release we'd like to ensure they can
actually _be used_ by Flink users. To achieve this the release managers ensure
that an issue for cross team testing is created in the Apache Flink Jira. This
can and should be picked up by other community members to verify the
functionality and usability of the feature.
The issue should contain some entry points which enables other community
members to test it. It should not contain documentation on how to use the
feature as this should be part of the actual documentation. The cross team
tests are performed after the feature freeze. Documentation should be in place
before that. Those tests are manual tests, so do not confuse them with
automated tests.
To sum that up:
* User facing features should be tested by other contributors
* The scope is usability and sanity of the feature
* The feature needs to be already documented
* The contributor creates an issue containing some pointers on how to get
started (e.g. link to the documentation, suggested targets of verification)
* Other community members pick those issues up and provide feedback
* Cross team testing happens right after the feature freeze
h3. Expectations
* Jira issues for each expected release task according to the release plan is
created and labeled as {{{}release-testing{}}}.
* All the created release-testing-related Jira issues are resolved and the
corresponding blocker issues are fixed.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (FLINK-35680) CLONE - Review Release Notes in JIRA
Weijie Guo created FLINK-35680:
--
Summary: CLONE - Review Release Notes in JIRA
Key: FLINK-35680
URL: https://issues.apache.org/jira/browse/FLINK-35680
Project: Flink
Issue Type: Sub-task
Reporter: Weijie Guo
Assignee: lincoln lee
JIRA automatically generates Release Notes based on the {{Fix Version}} field
applied to issues. Release Notes are intended for Flink users (not Flink
committers/contributors). You should ensure that Release Notes are informative
and useful.
Open the release notes from the version status page by choosing the release
underway and clicking Release Notes.
You should verify that the issues listed automatically by JIRA are appropriate
to appear in the Release Notes. Specifically, issues should:
* Be appropriately classified as {{{}Bug{}}}, {{{}New Feature{}}},
{{{}Improvement{}}}, etc.
* Represent noteworthy user-facing changes, such as new functionality,
backward-incompatible API changes, or performance improvements.
* Have occurred since the previous release; an issue that was introduced and
fixed between releases should not appear in the Release Notes.
* Have an issue title that makes sense when read on its own.
Adjust any of the above properties to the improve clarity and presentation of
the Release Notes.
Ensure that the JIRA release notes are also included in the release notes of
the documentation (see section "Review and update documentation").
h4. Content of Release Notes field from JIRA tickets
To get the list of "release notes" field from JIRA, you can ran the following
script using JIRA REST API (notes the maxResults limits the number of entries):
{code:bash}
curl -s
https://issues.apache.org/jira//rest/api/2/search?maxResults=200=project%20%3D%20FLINK%20AND%20%22Release%20Note%22%20is%20not%20EMPTY%20and%20fixVersion%20%3D%20${RELEASE_VERSION}
| jq '.issues[]|.key,.fields.summary,.fields.customfield_12310192' | paste - -
-
{code}
{{jq}} is present in most Linux distributions and on MacOS can be installed
via brew.
h3. Expectations
* Release Notes in JIRA have been audited and adjusted
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (FLINK-35682) CLONE - Create a release branch
Weijie Guo created FLINK-35682:
--
Summary: CLONE - Create a release branch
Key: FLINK-35682
URL: https://issues.apache.org/jira/browse/FLINK-35682
Project: Flink
Issue Type: Sub-task
Affects Versions: 1.19.0
Reporter: Weijie Guo
Assignee: lincoln lee
Fix For: 1.19.0
If you are doing a new minor release, you need to update Flink version in the
following repositories and the [AzureCI project
configuration|https://dev.azure.com/apache-flink/apache-flink/]:
* [apache/flink|https://github.com/apache/flink]
* [apache/flink-docker|https://github.com/apache/flink-docker]
* [apache/flink-benchmarks|https://github.com/apache/flink-benchmarks]
Patch releases don't require the these repositories to be touched. Simply
checkout the already existing branch for that version:
{code:java}
$ git checkout release-$SHORT_RELEASE_VERSION
{code}
h4. Flink repository
Create a branch for the new version that we want to release before updating the
master branch to the next development version:
{code:bash}
$ cd ./tools
tools $ releasing/create_snapshot_branch.sh
tools $ git checkout master
tools $ OLD_VERSION=$CURRENT_SNAPSHOT_VERSION
NEW_VERSION=$NEXT_SNAPSHOT_VERSION releasing/update_branch_version.sh
{code}
In the {{master}} branch, add a new value (e.g. {{v1_16("1.16")}}) to
[apache-flink:flink-annotations/src/main/java/org/apache/flink/FlinkVersion|https://github.com/apache/flink/blob/master/flink-annotations/src/main/java/org/apache/flink/FlinkVersion.java]
as the last entry:
{code:java}
// ...
v1_12("1.12"),
v1_13("1.13"),
v1_14("1.14"),
v1_15("1.15"),
v1_16("1.16");
{code}
Additionally in master, update the branch list of the GitHub Actions nightly
workflow (see
[apache/flink:.github/workflows/nightly-trigger.yml#L31ff|https://github.com/apache/flink/blob/master/.github/workflows/nightly-trigger.yml#L31]):
The two most-recent releases and master should be covered.
The newly created branch and updated {{master}} branch need to be pushed to the
official repository.
h4. Flink Docker Repository
Afterwards fork off from {{dev-master}} a {{dev-x.y}} branch in the
[apache/flink-docker|https://github.com/apache/flink-docker] repository. Make
sure that
[apache/flink-docker:.github/workflows/ci.yml|https://github.com/apache/flink-docker/blob/dev-master/.github/workflows/ci.yml]
points to the correct snapshot version; for {{dev-x.y}} it should point to
{{{}x.y-SNAPSHOT{}}}, while for {{dev-master}} it should point to the most
recent snapshot version (\{[$NEXT_SNAPSHOT_VERSION}}).
After pushing the new minor release branch, as the last step you should also
update the documentation workflow to also build the documentation for the new
release branch. Check [Managing
Documentation|https://cwiki.apache.org/confluence/display/FLINK/Managing+Documentation]
on details on how to do that. You may also want to manually trigger a build to
make the changes visible as soon as possible.
h4. Flink Benchmark Repository
First of all, checkout the {{master}} branch to {{dev-x.y}} branch in
[apache/flink-benchmarks|https://github.com/apache/flink-benchmarks], so that
we can have a branch named {{dev-x.y}} which could be built on top of
(${{CURRENT_SNAPSHOT_VERSION}}).
Then, inside the repository you need to manually update the {{flink.version}}
property inside the parent *pom.xml* file. It should be pointing to the most
recent snapshot version ($NEXT_SNAPSHOT_VERSION). For example:
{code:xml}
1.18-SNAPSHOT
{code}
h4. AzureCI Project Configuration
The new release branch needs to be configured within AzureCI to make azure
aware of the new release branch. This matter can only be handled by Ververica
employees since they are owning the AzureCI setup.
h3. Expectations (Minor Version only if not stated otherwise)
* Release branch has been created and pushed
* Changes on the new release branch are picked up by [Azure
CI|https://dev.azure.com/apache-flink/apache-flink/_build?definitionId=1&_a=summary]
* {{master}} branch has the version information updated to the new version
(check pom.xml files and
*
[apache-flink:flink-annotations/src/main/java/org/apache/flink/FlinkVersion|https://github.com/apache/flink/blob/master/flink-annotations/src/main/java/org/apache/flink/FlinkVersion.java]
enum)
*
[apache/flink:.github/workflows/nightly-trigger.yml#L31ff|https://github.com/apache/flink/blob/master/.github/workflows/nightly-trigger.yml#L31]
should have the new release branch included
* New version is added to the
[apache-flink:flink-annotations/src/main/java/org/apache/flink/FlinkVersion|https://github.com/apache/flink/blob/master/flink-annotations/src/main/java/org/apache/flink/FlinkVersion.java]
enum.
* Make sure [flink-docker|https://github.com/apache/flink-docker/] has
{{dev-x.y}} branch and docker e2e tests run against this branch in the
corresponding
[jira] [Created] (FLINK-35681) CLONE - Select executing Release Manager
Weijie Guo created FLINK-35681:
--
Summary: CLONE - Select executing Release Manager
Key: FLINK-35681
URL: https://issues.apache.org/jira/browse/FLINK-35681
Project: Flink
Issue Type: Sub-task
Components: Release System
Affects Versions: 1.19.0
Reporter: Weijie Guo
Assignee: lincoln lee
Fix For: 1.19.0
h4. GPG Key
You need to have a GPG key to sign the release artifacts. Please be aware of
the ASF-wide [release signing
guidelines|https://www.apache.org/dev/release-signing.html]. If you don’t have
a GPG key associated with your Apache account, please create one according to
the guidelines.
Determine your Apache GPG Key and Key ID, as follows:
{code:java}
$ gpg --list-keys
{code}
This will list your GPG keys. One of these should reflect your Apache account,
for example:
{code:java}
--
pub 2048R/845E6689 2016-02-23
uid Nomen Nescio
sub 2048R/BA4D50BE 2016-02-23
{code}
In the example above, the key ID is the 8-digit hex string in the {{pub}} line:
{{{}845E6689{}}}.
Now, add your Apache GPG key to the Flink’s {{KEYS}} file in the [Apache Flink
release KEYS file|https://dist.apache.org/repos/dist/release/flink/KEYS]
repository at [dist.apache.org|http://dist.apache.org/]. Follow the
instructions listed at the top of these files. (Note: Only PMC members have
write access to the release repository. If you end up getting 403 errors ask on
the mailing list for assistance.)
Configure {{git}} to use this key when signing code by giving it your key ID,
as follows:
{code:java}
$ git config --global user.signingkey 845E6689
{code}
You may drop the {{--global}} option if you’d prefer to use this key for the
current repository only.
You may wish to start {{gpg-agent}} to unlock your GPG key only once using your
passphrase. Otherwise, you may need to enter this passphrase hundreds of times.
The setup for {{gpg-agent}} varies based on operating system, but may be
something like this:
{code:bash}
$ eval $(gpg-agent --daemon --no-grab --write-env-file $HOME/.gpg-agent-info)
$ export GPG_TTY=$(tty)
$ export GPG_AGENT_INFO
{code}
h4. Access to Apache Nexus repository
Configure access to the [Apache Nexus
repository|https://repository.apache.org/], which enables final deployment of
releases to the Maven Central Repository.
# You log in with your Apache account.
# Confirm you have appropriate access by finding {{org.apache.flink}} under
{{{}Staging Profiles{}}}.
# Navigate to your {{Profile}} (top right drop-down menu of the page).
# Choose {{User Token}} from the dropdown, then click {{{}Access User
Token{}}}. Copy a snippet of the Maven XML configuration block.
# Insert this snippet twice into your global Maven {{settings.xml}} file,
typically {{{}${HOME}/.m2/settings.xml{}}}. The end result should look like
this, where {{TOKEN_NAME}} and {{TOKEN_PASSWORD}} are your secret tokens:
{code:xml}
apache.releases.https
TOKEN_NAME
TOKEN_PASSWORD
apache.snapshots.https
TOKEN_NAME
TOKEN_PASSWORD
{code}
h4. Website development setup
Get ready for updating the Flink website by following the [website development
instructions|https://flink.apache.org/contributing/improve-website.html].
h4. GNU Tar Setup for Mac (Skip this step if you are not using a Mac)
The default tar application on Mac does not support GNU archive format and
defaults to Pax. This bloats the archive with unnecessary metadata that can
result in additional files when decompressing (see [1.15.2-RC2 vote
thread|https://lists.apache.org/thread/mzbgsb7y9vdp9bs00gsgscsjv2ygy58q]).
Install gnu-tar and create a symbolic link to use in preference of the default
tar program.
{code:bash}
$ brew install gnu-tar
$ ln -s /usr/local/bin/gtar /usr/local/bin/tar
$ which tar
{code}
h3. Expectations
* Release Manager’s GPG key is published to
[dist.apache.org|http://dist.apache.org/]
* Release Manager’s GPG key is configured in git configuration
* Release Manager's GPG key is configured as the default gpg key.
* Release Manager has {{org.apache.flink}} listed under Staging Profiles in
Nexus
* Release Manager’s Nexus User Token is configured in settings.xml
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (FLINK-35676) CLONE - Create a new version in JIRA
Weijie Guo created FLINK-35676:
--
Summary: CLONE - Create a new version in JIRA
Key: FLINK-35676
URL: https://issues.apache.org/jira/browse/FLINK-35676
Project: Flink
Issue Type: Sub-task
Reporter: Weijie Guo
Assignee: Matthias Pohl
When contributors resolve an issue in JIRA, they are tagging it with a release
that will contain their changes. With the release currently underway, new
issues should be resolved against a subsequent future release. Therefore, you
should create a release item for this subsequent release, as follows:
# In JIRA, navigate to the [Flink > Administration >
Versions|https://issues.apache.org/jira/plugins/servlet/project-config/FLINK/versions].
# Add a new release: choose the next minor version number compared to the one
currently underway, select today’s date as the Start Date, and choose Add.
(Note: Only PMC members have access to the project administration. If you do
not have access, ask on the mailing list for assistance.)
h3. Expectations
* The new version should be listed in the dropdown menu of {{fixVersion}} or
{{affectedVersion}} under "unreleased versions" when creating a new Jira issue.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (FLINK-35677) CLONE - Triage release-blocking issues in JIRA
Weijie Guo created FLINK-35677: -- Summary: CLONE - Triage release-blocking issues in JIRA Key: FLINK-35677 URL: https://issues.apache.org/jira/browse/FLINK-35677 Project: Flink Issue Type: Sub-task Reporter: Weijie Guo There could be outstanding release-blocking issues, which should be triaged before proceeding to build a release candidate. We track them by assigning a specific Fix version field even before the issue resolved. The list of release-blocking issues is available at the version status page. Triage each unresolved issue with one of the following resolutions: * If the issue has been resolved and JIRA was not updated, resolve it accordingly. * If the issue has not been resolved and it is acceptable to defer this until the next release, update the Fix Version field to the new version you just created. Please consider discussing this with stakeholders and the dev@ mailing list, as appropriate. ** When using "Bulk Change" functionality of Jira *** First, add the newly created version to Fix Version for all unresolved tickets that have old the old version among its Fix Versions. *** Afterwards, remove the old version from the Fix Version. * If the issue has not been resolved and it is not acceptable to release until it is fixed, the release cannot proceed. Instead, work with the Flink community to resolve the issue. h3. Expectations * There are no release blocking JIRA issues -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (FLINK-35675) Prepare Flink 1.20 Release
Weijie Guo created FLINK-35675:
--
Summary: Prepare Flink 1.20 Release
Key: FLINK-35675
URL: https://issues.apache.org/jira/browse/FLINK-35675
Project: Flink
Issue Type: New Feature
Components: Release System
Affects Versions: 1.19.0
Reporter: Weijie Guo
Assignee: lincoln lee
Fix For: 1.19.0
This umbrella issue is meant as a test balloon for moving the [release
documentation|https://cwiki.apache.org/confluence/display/FLINK/Creating+a+Flink+Release]
into Jira.
h3. Prerequisites
h4. Environment Variables
Commands in the subtasks might expect some of the following enviroment
variables to be set accordingly to the version that is about to be released:
{code:bash}
RELEASE_VERSION="1.5.0"
SHORT_RELEASE_VERSION="1.5"
CURRENT_SNAPSHOT_VERSION="$SHORT_RELEASE_VERSION-SNAPSHOT"
NEXT_SNAPSHOT_VERSION="1.6-SNAPSHOT"
SHORT_NEXT_SNAPSHOT_VERSION="1.6"
{code}
h4. Build Tools
All of the following steps require to use Maven 3.8.6 and Java 8. Modify your
PATH environment variable accordingly if needed.
h4. Flink Source
* Create a new directory for this release and clone the Flink repository from
Github to ensure you have a clean workspace (this step is optional).
* Run {{mvn -Prelease clean install}} to ensure that the build processes that
are specific to that profile are in good shape (this step is optional).
The rest of this instructions assumes that commands are run in the root (or
{{./tools}} directory) of a repository on the branch of the release version
with the above environment variables set.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: jira account permission
Hi Zhengke, You can fill in information on this page: https://selfserve.apache.org/jira-account.html to request a JIRA account. If you are new and want to contribute to Apache Flink, you can refer to the contribution guide here[1]. Wish you a great experience! refer: [1] https://flink.apache.org/how-to-contribute/overview/ Best, Zhongqiang Gong zhengke zhou 于2024年6月24日周一 02:05写道： > Hi Guys > > I want to contribute to Apache Flink. > Would you please give me the permission as a contributor? > My JIRA ID is zzzk1. >
[jira] [Created] (FLINK-35674) MySQL connector may cause deadlock issues when searching for binlog timestamps
Thorne created FLINK-35674: -- Summary: MySQL connector may cause deadlock issues when searching for binlog timestamps Key: FLINK-35674 URL: https://issues.apache.org/jira/browse/FLINK-35674 Project: Flink Issue Type: Bug Components: Flink CDC Affects Versions: cdc-3.1.1 Environment: flink-cdc-3.1.x Reporter: Thorne Fix For: cdc-3.2.0 Attachments: A7AE0D63-365D-4572-B63D-96DF5F096BF9.png, BF180441-9C61-40eb-B07C-A11F8BCEC2D0.png, FBA32597-8783-4678-B391-E450148C1B30.png When a task is started by multiple mysql connector timestamp start mode at the same time, when searching for binlog timestamp, there will be task blocking problem, which may cause source to be unable to obtain data all the time. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (FLINK-35673) TestFileSource$TestFileSourceBuilder cannot be cast to class FileSource$FileSourceBuilder
Weijie Guo created FLINK-35673: -- Summary: TestFileSource$TestFileSourceBuilder cannot be cast to class FileSource$FileSourceBuilder Key: FLINK-35673 URL: https://issues.apache.org/jira/browse/FLINK-35673 Project: Flink Issue Type: Bug Components: Tests Affects Versions: 1.20.0 Reporter: Weijie Guo Assignee: Weijie Guo -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (FLINK-35672) testPreAggregatedSlidingTimeWindow failed due to due to checkpoint expired before completing
Weijie Guo created FLINK-35672: -- Summary: testPreAggregatedSlidingTimeWindow failed due to due to checkpoint expired before completing Key: FLINK-35672 URL: https://issues.apache.org/jira/browse/FLINK-35672 Project: Flink Issue Type: Bug Components: Build System / CI Affects Versions: 1.20.0 Reporter: Weijie Guo -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (FLINK-35671) Support Iceberg CDC Pipeline Sink
Muhammet Orazov created FLINK-35671: --- Summary: Support Iceberg CDC Pipeline Sink Key: FLINK-35671 URL: https://issues.apache.org/jira/browse/FLINK-35671 Project: Flink Issue Type: Improvement Components: Flink CDC Reporter: Muhammet Orazov Similar to other [CDC pipeline sinks|https://nightlies.apache.org/flink/flink-cdc-docs-master/docs/connectors/pipeline-connectors/overview/], we should support Iceberg as a pipeline sink. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (FLINK-35670) Support Postgres Pipeline Source
Muhammet Orazov created FLINK-35670: --- Summary: Support Postgres Pipeline Source Key: FLINK-35670 URL: https://issues.apache.org/jira/browse/FLINK-35670 Project: Flink Issue Type: Improvement Components: Flink CDC Reporter: Muhammet Orazov Similar to other CDC pipeline sources (only MySQL at the moment), we should support Postgres as a pipeline source. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [VOTE] FLIP-463: Schema Definition in CREATE TABLE AS Statement
+1 (non-binding) Best, Ferenc On Sunday, June 23rd, 2024 at 05:13, Yanquan Lv wrote: > > > Thnaks Sergio, +1 (non-binding) > > gongzhongqiang gongzhongqi...@apache.org 于2024年6月23日周日 10:06写道： > > > +1 (non-binding) > > > > Best, > > Zhongqiang Gong > > > > Sergio Pena ser...@confluent.io.invalid 于2024年6月21日周五 22:18写道： > > > > > Hi everyone, > > > > > > Thanks for all the feedback about FLIP-463: Schema Definition in CREATE > > > TABLE AS Statement [1]. The discussion thread is here [2]. > > > > > > I'd like to start a vote for it. The vote will be open for at least 72 > > > hours unless there is an objection or insufficient votes. The FLIP will > > > be > > > considered accepted if 3 binding votes (from active committers according > > > to > > > the Flink bylaws [3]) are gathered by the community. > > > > > > [1] > > > > https://cwiki.apache.org/confluence/display/FLINK/FLIP-463%3A+Schema+Definition+in+CREATE+TABLE+AS+Statement > > > > > [2] https://lists.apache.org/thread/1ryxxyyg3h9v4rbosc80zryvjk6c8k83 > > > [3] [ > > > > https://cwiki.apache.org/confluence/display/FLINK/Flink+Bylaws#FlinkBylaws-Approvals](https://cwiki.apache.org/confluence/display/FLINK/Flink+Bylaws#FlinkBylaws-Approvals) > > https://cwiki.apache.org/confluence/display/FLINK/Flink+Bylaws#FlinkBylaws-Approvals](https://cwiki.apache.org/confluence/display/FLINK/Flink+Bylaws%23FlinkBylaws-Approvals) > > > > > < > > > https://cwiki.apache.org/confluence/display/FLINK/Flink+Bylaws#FlinkBylaws-Approvals](https://cwiki.apache.org/confluence/display/FLINK/Flink+Bylaws%23FlinkBylaws-Approvals) > > > > > > < > > > > https://cwiki.apache.org/confluence/display/FLINK/Flink+Bylaws#FlinkBylaws-Approvals](https://cwiki.apache.org/confluence/display/FLINK/Flink+Bylaws%23FlinkBylaws-Approvals) > > > > > Thanks, > > > Sergio Peña
jira account permission
Hi Guys I want to contribute to Apache Flink. Would you please give me the permission as a contributor? My JIRA ID is zzzk1.
