Some more thoughts. I think we can try out a first release and decide if everything is ok along the way. I suppose that we should run tests with supported Ignite versions (perhaps not all) and provide results. And finally there will be a release vote.
Best regards, Ivan Pavlukhin пт, 7 февр. 2020 г. в 19:43, Denis Magda <dma...@apache.org>: > > Folks, have we agreed on the release process? Saikat, could you point all > of us to a related discussion. If my memory doesn't fail me Alex Goncharuk > also wanted to step in before we do the first release. > > - > Denis > > > On Fri, Feb 7, 2020 at 8:02 AM Saikat Maitra <saikat.mai...@gmail.com> > wrote: > > > Hi Nikolay, Ivan, Denis > > > > I think we can release for spring boot autoconfigure module. > > > > > > I will also go ahead and make release for flink ext. > > > > I have pending PR for flume and zeromq, if I can get review and approval I > > can go ahead and merge and release these modules as well. > > > > Regards > > Saikat > > > > On Fri, 7 Feb 2020 at 2:06 AM, Nikolay Izhikov <nizhi...@apache.org> > > wrote: > > > > > Thanks for clarification. > > > > > > Igniters, I will proceed with the release in the next few days if there > > is > > > no objections on it. > > > > > > > 7 февр. 2020 г., в 10:57, Ivan Pavlukhin <vololo...@gmail.com> > > > написал(а): > > > > > > > > Hi Nikolay, > > > > > > > > In fact I did not mean anything supernatural. A scheme you mentioned > > > >> I thought we just release module with the 1.0.0 version and specify > > > supported Ignite version somewhere in the documentation. > > > > sounds fine to me. > > > > > > > > Best regards, > > > > Ivan Pavlukhin > > > > > > > > чт, 6 февр. 2020 г. в 15:00, Nikolay Izhikov <nizhi...@apache.org>: > > > >> > > > >> Hello, Ivan. > > > >> > > > >>> 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. > > > >> > > > >> Please, clarify, what do you mean? > > > >> Do you have any idea how it should be implemented? > > > >> > > > >> I thought we just release module with the 1.0.0 version and specify > > > supported Ignite version somewhere in the documentation. > > > >> > > > >>> 6 февр. 2020 г., в 11:15, Ivan Pavlukhin <vololo...@gmail.com> > > > написал(а): > > > >>> > > > >>> 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 > > > >> > > > > > > > >
