Hey, I would like to raise an issue that happensa at couple of times during 1.5.0 RCx votings. There were some bug fixes like: https://issues.apache.org/jira/browse/FLINK-9349 <https://issues.apache.org/jira/browse/FLINK-9349> https://issues.apache.org/jira/browse/FLINK-9295 <https://issues.apache.org/jira/browse/FLINK-9295>
That were merged to release branch after creating some RC, they were marked with fix versions set to 1.5.1 and new when previous RC vote was cancelled and new RC was created, they sneaked into 1.5.0. Minor thing is that Jira issues should be updated accordingly. If you merge something to release branch, please pay attention to cancelled RCs and from which commit new RC is being created. Much bigger issue is that when such fixes are sneaking so late to the release, they do not go through normal release testing procedure. I don’t know how should we handle such situations, but if something like that happened to your commits during this 1.5.0, please double check them when new RC comes out. They might require some manual testing or running some end to end tests. I would propose that any merges to release branches during RC votes (after release testing kicked off) should go through release manager, so that he could decide whether to include such fixes or postpone them to next release. Maybe this would require to create separate release branches for 1.5.0 and 1.5.1. Piotrek
