Nikolay, Thank you for driving it! It is great to establish this process in practice earlier because it seems that we need to release a Flink integration soon because Ignite 2.8 is going to be released without that integration bundled.
As usual we need to decide about versioning and a correspondence to Ignite versions. As we are going to have a separate release cycle I can imagine an independent versioning scheme with a range of supported Ignite versions. Also I think it is a good idea to update ignite-extensions README on GitHub and provide a link to relevant TC jobs. Best regards, Ivan Pavlukhin ср, 5 февр. 2020 г. в 17:44, Denis Magda <dma...@apache.org>: > > Alex, did you have a chance to review Saikat’s changes related to the > extensions repository organization and release approach? > > Denis > > On Wednesday, February 5, 2020, Nikolay Izhikov <nizhi...@apache.org> wrote: > > > Hello, Igniters. > > > > We don't have a release process for newly created ignite-extensions > > modules. > > I want to release two modules: > > > > * ignite-spring-boot-autoconfigure > > * ignite-client-spring-boot-autoconfigure > > > > Let's discuss it. > > > > Any objections to it? > > What should be done before release? > > > > > -- > - > Denis
