ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Igor Sapego <isap...@apache.org>
Subject Re: Apache Ignite 2.5 release
Date Thu, 26 Apr 2018 16:45:05 GMT
Hi guys,
I also have fix for a critical bug [1] which I'd like to include
in this release. It is OK?

[1] - https://issues.apache.org/jira/browse/IGNITE-8394

Best Regards,
Igor

On Wed, Apr 25, 2018 at 8:19 PM, Andrey Gura <agura@apache.org> wrote:

> Pavel,
>
> looks like painful problem. I've targeted it to 2.5 release.
>
> Thanks!
>
> On Wed, Apr 25, 2018 at 8:15 PM, Dmitry Pavlov <dpavlov.spb@gmail.com>
> wrote:
> > Hi Pavel,
> >
> > +1 from me, assertion in GridCachePartitionExchangeManager is to be
> fixed
> > before release.
> >
> > Sincerely,
> > Dmitriy Pavlov
> >
> > ср, 25 апр. 2018 г. в 20:13, Pavel Kovalenko <jokserfn@gmail.com>:
> >
> >> Igniters,
> >>
> >> I've found blocker issue https://issues.apache.org/
> jira/browse/IGNITE-8390
> >> Cause of the problem is incorrect assertion that could be fixed very
> >> quickly.
> >> I would like to add this issue to 2.5 release.
> >>
> >> 2018-04-25 17:38 GMT+03:00 Andrey Gura <agura@apache.org>:
> >>
> >> > Igniters,
> >> >
> >> > We have about 30 JIRA issues that still aren't resolved. So it's
> >> > possible that release date will be changed.
> >> >
> >> > But I think that it's time for scope freeze. Please, don't target any
> >> > issues to 2.5 version without community approve.
> >> >
> >> > Thanks.
> >> >
> >> > On Fri, Apr 13, 2018 at 11:30 AM, Anton Vinogradov <av@apache.org>
> >> wrote:
> >> > > Andrey, thanks for control :)
> >> > >
> >> > > So, You'll fix broken versions eventually?
> >> > >
> >> > > BTW, I don't think it's a good idea to merge issues with fix version
> >> 2.5
> >> > to
> >> > > ignite-2.5. Good way is to fix version to 2.6 instead.
> >> > >
> >> > > 2018-04-12 21:34 GMT+03:00 Andrey Gura <agura@apache.org>:
> >> > >
> >> > >> Anton,
> >> > >>
> >> > >> all is under control.
> >> > >>
> >> > >> Branches will be compared and changes that should be included
to AI
> >> > >> 2.5 will be identified.
> >> > >>
> >> > >> On Thu, Apr 12, 2018 at 6:19 PM, Petr Ivanov <mr.weider@gmail.com>
> >> > wrote:
> >> > >> > Possibly it is Andrey Gura — he initiated this thread and
created
> >> > >> corresponding branch.
> >> > >> >
> >> > >> >
> >> > >> >> On 12 Apr 2018, at 17:39, Anton Vinogradov <av@apache.org>
> wrote:
> >> > >> >>
> >> > >> >> Release manager is responsible for this change.
> >> > >> >> Do we have release manager for 2.5?
> >> > >> >>
> >> > >> >> 2018-04-12 17:35 GMT+03:00 Dmitry Pavlov <dpavlov.spb@gmail.com
> >:
> >> > >> >>
> >> > >> >>> I've changed my ticket version assignment, and a
lot of
> Igniters
> >> > >> changed.
> >> > >> >>>
> >> > >> >>> Filter for double-check tickets related to you
> >> > >> >>> *https://issues.apache.org/jira/issues/?jql=project%
> >> > >> >>> 3DIGNITE%20AND%20fixVersion%3D2.5%20and%20resolution%20is%
> >> > >> >>> 20EMPTY%20%20and%20(assignee%3DcurrentUser()%20or%
> >> > >> >>> 20reporter%3DcurrentUser())
> >> > >> >>> <https://issues.apache.org/jira/issues/?jql=project%
> >> > >> >>> 3DIGNITE%20AND%20fixVersion%3D2.5%20and%20resolution%20is%
> >> > >> >>> 20EMPTY%20%20and%20(assignee%3DcurrentUser()%20or%
> >> > >> >>> 20reporter%3DcurrentUser())>*
> >> > >> >>>
> >> > >> >>>
> >> > >> >>> чт, 12 апр. 2018 г. в 17:24, Anton Vinogradov
<av@apache.org>:
> >> > >> >>>
> >> > >> >>>> 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.weider@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
<dmagda@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 <
> agura@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 <
> agura@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
> >> > >> >>>>>>>
> >> > >> >>>>>
> >> > >> >>>>>
> >> > >> >>>>
> >> > >> >>>
> >> > >> >
> >> > >>
> >> >
> >>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message