Hi Etienne, Which branch would you cut the release from?
I find the flink-connector-parent branches confusing. If I merge a PR to the ci_utils branch, would it immediately change the CI workflow of all of the connectors? If I merge something to the release_utils branch, would it immediately change the release process of all of the connectors? I would like to add the possibility of creating Python packages for the connectors [1]. This would consist of some common code, which should reside in flink-connector-parent, like: - scripts for running Python test - test infra. I expect that this would evolve in time - ci workflow - this would be more slow moving, but might change if the infra is charging - release scripts - this would be slow moving, but might change too. I think we should have a release for all of the above components, so the connectors could move forward on their own pace. What do you think? Thanks, Péter [1] https://issues.apache.org/jira/browse/FLINK-33528 On Thu, Nov 30, 2023, 16:55 Etienne Chauchot <echauc...@apache.org> wrote: > Thanks Sergey for your vote. Indeed I have listed only the PRs merged > since last release but there are these 2 open PRs that could be worth > reviewing/merging before release. > > https://github.com/apache/flink-connector-shared-utils/pull/25 > > https://github.com/apache/flink-connector-shared-utils/pull/20 > > Best > > Etienne > > > Le 30/11/2023 à 11:12, Sergey Nuyanzin a écrit : > > thanks for volunteering Etienne > > > > +1 for releasing > > however there is one more PR to enable custom jvm flags for connectors > > in similar way it is done in Flink main repo for modules > > It will simplify a bit support for java 17 > > > > could we have this as well in the coming release? > > > > > > > > On Wed, Nov 29, 2023 at 11:40 AM Etienne Chauchot<echauc...@apache.org> > > wrote: > > > >> Hi all, > >> > >> I would like to discuss making a v1.0.1 release of > flink-connector-parent. > >> > >> Since last release, there were only 2 changes: > >> > >> -https://github.com/apache/flink-connector-shared-utils/pull/19 > >> (spotless addition) > >> > >> -https://github.com/apache/flink-connector-shared-utils/pull/26 > >> (surefire configuration) > >> > >> The new release would bring the ability to skip some tests in the > >> connectors and among other things skip the archunit tests. It is > >> important for connectors to skip archunit tests when tested against a > >> version of Flink that changes the archunit rules leading to a change of > >> the violation store. As there is only one violation store and the > >> connector needs to be tested against last 2 minor Flink versions, only > >> the version the connector was built against needs to run the archunit > >> tests and have them reflected in the violation store. > >> > >> > >> I volunteer to make the release. As it would be my first ASF release, I > >> might require the guidance of one of the PMC members. > >> > >> > >> Best > >> > >> Etienne > >> > >> > >> > >> > >>
