Re: IGNITE-12702 - Discussion

2020-06-08 Thread Ilya Kasnacheev
Hello! Unfortunately your merged change is not visible in this PR (0 files changed). Please create your pull request off your feature branch, not master. Regards, -- Ilya Kasnacheev вс, 7 июн. 2020 г. в 20:20, kartik somani : > Hello, > > I have created a pull request for this issue > < >

Re: IGNITE-12702 - Discussion

2020-06-07 Thread kartik somani
Hello, I have created a pull request for this issue : https://github.com/apache/ignite/pull/7882 Can someone review? Regards, Kartik On Mon, Apr 20, 2020 at

Re: IGNITE-12702 - Discussion

2020-04-20 Thread kartik somani
Hello Igniters, I have created pull request for IGNITE-12702. Can someone review this? https://github.com/apache/ignite/pull/7663 regards, Kartik On Mon, Mar 23, 2020 at 11:28 PM Denis Magda wrote: > Hi Kartik, > > Actually, it means quite the opposite. You should fill in the release notes >

Re: IGNITE-12702 - Discussion

2020-03-24 Thread kartik somani
Thank you for the clarification On Mon, Mar 23, 2020, 11:28 PM Denis Magda wrote: > Hi Kartik, > > Actually, it means quite the opposite. You should fill in the release notes > field before the ticket is resolved/closed so that a release manager of a > next Ignite version adds a proper line to

Re: IGNITE-12702 - Discussion

2020-03-23 Thread Denis Magda
Hi Kartik, Actually, it means quite the opposite. You should fill in the release notes field before the ticket is resolved/closed so that a release manager of a next Ignite version adds a proper line to the final release notes with all the changes. As for the docs, it's highly likely you don't

IGNITE-12702 - Discussion

2020-03-22 Thread kartik somani
Hello Igniters, I want to start working on ticket IGNITE-12702 . The flags on this issue are "Docs Required, Release Notes Required". Does this mean I have to first write/get docs and release notes before starting work on this? Regards, Kartik