THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
To create your own FLIP, click on "Create" on the header and choose "FLIP-Template" other than "Blank page".
Table of Contents
Purpose
The purpose of FLIPs is to have a central place to collect and document planned major enhancements to Apache Flink. While JIRA is still the tool to track tasks, bugs, and progress, the FLIPs give an accessible high level overview of the result of design discussions and proposals. Think of FLIPs as collections of major design documents for user-relevant changes.
...
- Create a page which is a child of this one. Take the next available FLIP number (below) and give your proposal a descriptive heading. e.g. "FLIP 42: Enable Flink Streaming Jobs to stop gracefully". If you don't have the necessary permissions for creating a new page, please ask on the development mailing list.
- Fill in the sections as described above
- Start a [DISCUSS] thread on the Apache mailing list. Please ensure that the subject of the thread is of the format [DISCUSS] FLIP-{your FLIP number} {your FLIP heading} The discussion should happen on the mailing list not on the wiki since the wiki comment system doesn't work well for larger discussions. In the process of the discussion you may update the proposal. You should let people know the changes you are making.
- Once the proposal is finalized call a [VOTE] to have the proposal adopted. These proposals are more serious than code changes and more serious even than release votes. The criteria for acceptance is consensus.
- Please update the FLIP wiki page , and the index below, to reflect the current stage of the FLIP after a vote. This acts as the permanent record indicating the result of the FLIP (e.g., Accepted or Rejected). Also report the result of the FLIP vote to the voting thread on the mailing list so the conclusion is clear.
FLIP round-up
Next FLIP Number: 261
Other free numbers: 178,230
Use this number as the identifier for your FLIP and increment this value.
Adopted/Accepted but unreleased FLIPs
...
...
...
...
Discussion thread: http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/DISCUSS-FLIP-130-Support-for-Python-DataStream-API-Stateless-Part-td43035.html
...
FLIP-133: Rework PyFlink Documentation
...
Discussion thread: https://lists.apache.org/thread.html/redebc9d1281edaa4a1fbf0d8c76a69fcff574b0496e78519840a5a61%40%3Cdev.flink.apache.org%3E
...
Discussion thread: http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/DISCUSS-FLIP-137-Support-Pandas-UDAF-in-PyFlink-tt44060.html
...
Discussion thread: http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/DISCUSS-FLIP-139-General-Python-User-Defined-Aggregate-Function-on-Table-API-td44139.html
...
...
...
...
...
...
Vote: https://lists.apache.org/thread/2087m6t1d58lw3xngtwhws6xbd9fm30r
...
Vote: https://lists.apache.org/thread/pq1ot6wj1j87jxm4tqydl4vf6klqsy4l
...
Vote: https://lists.apache.org/thread/k6zol3fp59q16ogsg9xmjx5j9yp98dj9
...
Vote: https://lists.apache.org/thread/899vt2momfqpn65zmx6cq74o3qn41yf1
...
...
Discuss: https://lists.apache.org/thread/n8v32j6o3d50mpblxydbz82q1q436ob4
Vote: https://lists.apache.org/thread/rxxxq0q9v9pmzd2ht9nybpg5vrzyhwx7
...
discuss: https://lists.apache.org/thread/zw2crf0c7t7t4cb5cwcwjpvsb3r1ovz2
vote: https://lists.apache.org/thread/tpyros2fl0howbtcb3fc54f7b7pjn1fw
...
discuss: https://lists.apache.org/thread/gjgr3b3w2c379ny7on3khjgwyjp2gyq1
vote: https://lists.apache.org/thread/vsn21hmmv1km2ybl3hq00p7nhrp1dnsw
It's not unusual for a FLIP proposal to take long discussions to be finalized. Below are some general suggestions on driving FLIPs towards consensus. Notice that these are hints rather than rules. Contributors should make pragmatic decisions in accordance with individual situations.
- The progress of a FLIP should not be long blocked on an unresponsive reviewer. A reviewer who blocks a FLIP with dissenting opinions should try to respond to the subsequent replies timely, or at least provide a reasonable estimated time to respond.
- A typical reasonable time to wait for responses is 1 week, but be pragmatic about it. Also, it would be considerate to wait longer during holiday seasons (e.g., Christmas, Chinese New Year, etc.).
- We encourage FLIP proposers to actively reach out to the interested parties (e.g., previous contributors of the relevant part) early. It helps expose and address the potential dissenting opinions early, and also leaves more time for other parties to respond while the proposer works on the FLIP.
- Committers should use their veto rights with care. According to the ASF policy, vetos must be provided with a technical justification showing why the change is bad. They should not be used for simply blocking the process so the voter has more time to catch up.
FLIP round-up
Next FLIP Number: 422
Other free numbers:
Use this number as the identifier for your FLIP and increment this value.
...
discuss: https://lists.apache.org/thread/k19bn7gq5jth3jn9h3zkcyrk44hv5nyn
...
Under discussion
Page properties report headings Discussion thread sortBy Title cql label = "discussion" and space = currentSpace()
...
Page properties report headings Release,JIRA sortBy Title cql label = "accepted" and space = currentSpace()
Released
...
| title | 1.15 |
|---|
...
Released
...
Page properties report headings Release,JIRA sortBy Title cql label = "released" and space = currentSpace()
...