ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dmitriy Pavlov <dpavlov....@gmail.com>
Subject Re: Apache Ignite 2.7 release
Date Thu, 20 Sep 2018 10:00:11 GMT
yep, someone can use his or her @gridgain address, even it is not best
practice and Apache recommends to avoid it. It is still an individual in
the Community.

I've checked the history of the ticket and there was a strange reassignment
in it. we'll try to find out if it is under review. Hopefully, contributor
assigned this ticket can come and comment.

чт, 20 сент. 2018 г. в 12:48, Paul Anderson <deviljelly@gmail.com>:

> ok... thought I saw gridgain interaction in an email.... Will start a new
> thread with my questions on test code or comment on Jira
>
> On Thu, Sep 20, 2018 at 11:39 AM Dmitriy Pavlov <dpavlov.spb@gmail.com>
> wrote:
>
> > Hi Paul,
> >
> > Please be more specific, GridGain can't take part in the community, only
> > individual contributors can. So I don't understand which contributor was
> > pulling 9298.
> >
> > Any feedback is appreciated, especially constructive, cause it helps in
> > developing a product in the right direction. But we can't enforce someone
> > to do something faster or in more right manner. Why don't suggest help
> > instead?
> >
> > Sincerely,
> > Dmitriy Pavlov
> >
> > чт, 20 сент. 2018 г. в 12:29, Paul Anderson <deviljelly@gmail.com>:
> >
> > > Dimitiry, Re: IGNITE-9298 ... this is my first contribution, don't know
> > who
> > > is reviewing the code, I did see that it was pulled by GridGain.
> > >
> > > Additionally I was not happy about the test code, I followed what was
> > there
> > > before but it doesn't seem right.
> > >
> > > On Thu, Sep 20, 2018 at 9:17 AM Dmitriy Pavlov <dpavlov.spb@gmail.com>
> > > wrote:
> > >
> > > > Hi,
> > > >
> > > > As always, our constraint is a review. We as the community seems to
> > agree
> > > > that review and patch commenting is a major contribution, but very
> few
> > of
> > > > us doing a review, and 92 tickets are in Patch Available state.
> > > >
> > > >
> > > >
> > >
> >
> https://cwiki.apache.org/confluence/display/IGNITE/Issues+waiting+for+review
> > > >
> > > >
> > > > Everyone can help, so tests run can be checked (e.g. in the TC Bot);
> > code
> > > > style; change itself is clear and relates to issue. Don't forget to
> > share
> > > > positive things that you like in PR/Change, does not point to
> problems
> > > > only.
> > > >
> > > > So if a ticket is accepted and merged there is usually no reason to
> > move
> > > it
> > > > to the next version instead of the nearest one.
> > > >
> > > > Sincerely,
> > > > Dmitriy Pavlov
> > > >
> > > > чт, 20 сент. 2018 г. в 3:54, Ray <rayliu@cisco.com>:
> > > >
> > > > > Hello, Igniters.
> > > > >
> > > > > Is there any specific reason why this ticket is removed from 2.7
> > scope?
> > > > > I think this ticket is important for both usability and
> performance.
> > > > > Without this ticket, we have to create an index manually identical
> to
> > > > > primary key if we want to use SQL query.
> > > > > https://issues.apache.org/jira/browse/IGNITE-8386
> > > > >
> > > > >
> > > > >
> > > > > --
> > > > > Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
> > > > >
> > > >
> > >
> >
>

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