Folks, I see a lot of issues resolved as 2.5 but not merged to ignite-2.5 branch.
Who is in charge of release 2.5, why (first time in history) nobody changes all 2.5 to 2.6? 2018-04-06 10:19 GMT+03:00 Petr Ivanov <mr.wei...@gmail.com>: > Added corresponding triggers for ignite-2.5 in Ignite Tests 2.4+ project > in TC. > > > > > On 5 Apr 2018, at 21:55, Denis Magda <dma...@apache.org> wrote: > > > > Thanks Andrey! > > > > Folks, if you'd like to add anything to 2.5 please make sure it gets > merged > > into 2.5 branch. > > > > -- > > Denis > > > > On Thu, Apr 5, 2018 at 11:29 AM, Andrey Gura <ag...@apache.org> wrote: > > > >> Hi, > >> > >> I've created branch ignite-2.5 for Apache Ignite 2.5 release. > >> > >> As always please follow the rules below when merging new commits to > master: > >> > >> 1) If ticket is targeted for 2.5 release, please merge to master, then > >> cherry-pick to ignite-2.5 > >> 2) Otherwise just merge to master. > >> > >> > >> > >> On Wed, Apr 4, 2018 at 9:11 PM, Andrey Gura <ag...@apache.org> wrote: > >>> Igniters, > >>> > >>> It's time to create branch for upcoming Apache Ignite 2.5 release in > >>> order to start stabilization process. > >>> > >>> If there are no any objections I'll create ignite-2.5 branch tomorrow. > >>> > >>> Also please check JIRA issues assigned to you and move it to the next > >>> version if this issues shouldn't be included to 2.5 release. > >>> > >>> Release page on wiki [1] contains all issues targeted to 2.5 (fix > >>> version field). > >>> > >>> [1] https://cwiki.apache.org/confluence/display/IGNITE/ > Apache+Ignite+2.5 > >> > >
