ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Vladimir Ozerov <voze...@gridgain.com>
Subject Re: Halfway to Ignite 1.6
Date Wed, 18 May 2016 11:52:26 GMT
Fix is merged. Thank you.

On Wed, May 18, 2016 at 2:24 PM, Anton Vinogradov <av@apache.org> wrote:

> Ok, will pause Vote preparation untill you merge fix.
>
> On Wed, May 18, 2016 at 2:21 PM, Vladimir Ozerov <vozerov@gridgain.com>
> wrote:
>
> > Hi,
> >
> > I need to merge one more fix for Hadoop -
> > https://issues.apache.org/jira/browse/IGNITE-3165
> > Will do that in the nearest hour.
> >
> > Vladimir.
> >
> > On Wed, May 18, 2016 at 1:37 PM, Anton Vinogradov <
> > avinogradov@gridgain.com>
> > wrote:
> >
> > > Since everything already merged, ignite-1.6 code freezed since this
> > moment.
> > > Each fix should be allowed at this thread before push.
> > >
> > > On Wed, May 18, 2016 at 12:59 PM, Alexey Kuznetsov <
> > > akuznetsov@gridgain.com>
> > > wrote:
> > >
> > > > I do one more review of IGNITE-1371 (
> > > > https://issues.apache.org/jira/browse/IGNITE-1371),
> > > >  fixed minor problems (like missing ASF headers and typos) and merged
> > > into
> > > > ignite-1.6.
> > > >
> > > > But we need:
> > > >  1) Create issue for refactoring of serializers as I mentioned in
> JIRA
> > > > comment.
> > > >  2) Create a test suite and configure it to run on
> > ci.ignite.apache.org
> > > >  3) Describe how this module could be manually tested.
> > > >
> > > >
> > > > On Wed, May 18, 2016 at 8:54 AM, Dmitriy Setrakyan <
> > > dsetrakyan@apache.org>
> > > > wrote:
> > > >
> > > > > Cos, I agree that it would be nice to merge IGNITE-1371
> > > > > <https://issues.apache.org/jira/browse/IGNITE-1371>. However,
if
> > there
> > > > are
> > > > > more fixes and review comments, I would schedule it for the next
> > > > release. I
> > > > > guess Alexey, Anton, and Igor and better judges on it. Guys, can
> you
> > > > please
> > > > > comment?
> > > > >
> > > > > As it was noted in another thread, we are way overdue for this
> > release
> > > > and
> > > > > it already has plenty of new features and bug fixes. Let’s hope
> that
> > we
> > > > can
> > > > > close out everything in PATCH_AVAILABLE status soon and send it out
> > > for a
> > > > > vote.
> > > > >
> > > > > D.
> > > > >
> > > > > On Tue, May 17, 2016 at 5:20 PM, Konstantin Boudnik <
> cos@apache.org>
> > > > > wrote:
> > > > >
> > > > > > You can still talk about the release even if it is in the final
> > > stages.
> > > > > > What
> > > > > > would be unfortunate is to miss some of the good features (like
> > > > > > IGNITE-1371)
> > > > > > just because of an arbitrary date of an even of some kind, which
> > has
> > > no
> > > > > > relevance to the project itself.
> > > > > >
> > > > > > For what it worth, rushing releases (ie a product company way
of
> > > > > > satisfying a
> > > > > > time-boxed effort, aka PM-lust for scheduling) tends to end
up
> in a
> > > > > > substantially lower quality of the releases.
> > > > > >
> > > > > > Cos
> > > > > >
> > > > > > On Mon, May 16, 2016 at 05:09PM, Dmitriy Setrakyan wrote:
> > > > > > > I will be presenting at IMC Summit next week in Bay Area,
and
> it
> > > sure
> > > > > > would
> > > > > > > be nice to talk about 1.6 release and the new features.
Would
> be
> > > > great
> > > > > if
> > > > > > > we could send it for vote on Wednesday morning. This would
> give a
> > > > > chance
> > > > > > > for the vote to pass by EOD on Friday, if everything is
OK.
> > > > > > >
> > > > > > > D.
> > > > > > >
> > > > > > > On Mon, May 16, 2016 at 7:50 AM, Sergey Kozlov <
> > > skozlov@gridgain.com
> > > > >
> > > > > > wrote:
> > > > > > >
> > > > > > > > Guys
> > > > > > > >
> > > > > > > > I'm concerned that we postpone once again the date
of code
> > > freeze.
> > > > It
> > > > > > > > shifts dates of testing and release and it seems we
won't be
> > able
> > > > to
> > > > > > send
> > > > > > > > to voting this week
> > > > > > > >
> > > > > > > > On Mon, May 16, 2016 at 5:43 PM, Anton Vinogradov
<
> > > > > > > > avinogradov@gridgain.com>
> > > > > > > > wrote:
> > > > > > > >
> > > > > > > > > Thanks everyone for checking!
> > > > > > > > >
> > > > > > > > > Only 8 tickets left!
> > > > > > > > >
> > > > > > > > > Seems contributors still need 1-2 days to pass
codereview
> and
> > > > merge
> > > > > > final
> > > > > > > > > changes.
> > > > > > > > > We postponed code freeze till Wednesday UTC 19-00.
Hope,
> this
> > > > will
> > > > > > be the
> > > > > > > > > last time.
> > > > > > > > >
> > > > > > > > > On Mon, May 16, 2016 at 3:56 PM, Anton Vinogradov
<
> > > > > > > > > avinogradov@gridgain.com>
> > > > > > > > > wrote:
> > > > > > > > >
> > > > > > > > > > Igniters,
> > > > > > > > > >
> > > > > > > > > > We still have 32 issues with status "In
Progress" or
> "Patch
> > > > > > Available"
> > > > > > > > > and
> > > > > > > > > > fixVersion = 1.6.
> > > > > > > > > > Full list
> > > > > > > > > > <
> > > > > > > > >
> > > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> https://issues.apache.org/jira/issues/?filter=-1&jql=(status%20%3D%20%22In%20Progress%22%20or%20status%20%3D%20%22Patch%20Available%22)%20AND%20fixVersion%20%3D%201.6%20and%20project%20%3D%20Ignite
> > > > > > > > >
> > > > > > > > > can
> > > > > > > > > > be found here.
> > > > > > > > > >
> > > > > > > > > > Please change fixVersion for issues can't
be resolved at
> > 1.6
> > > to
> > > > > > 1.7,
> > > > > > > > and
> > > > > > > > > > close other issues before code freeze.
> > > > > > > > > >
> > > > > > > > > > On Mon, May 16, 2016 at 12:57 AM, Andrey
Gura <
> > > > > agura@gridgain.com>
> > > > > > > > > wrote:
> > > > > > > > > >
> > > > > > > > > >> Guys,
> > > > > > > > > >>
> > > > > > > > > >> I've finished with improvements for
JDBC drivers [1]. I
> > hope
> > > > > > somebody
> > > > > > > > > will
> > > > > > > > > >> review and merge it before code freeze.
> > > > > > > > > >> Also I created issue related with query
execution from
> > > client
> > > > > > nodes
> > > > > > > > [2].
> > > > > > > > > >> It
> > > > > > > > > >> affects system behaviour that related
with [1] and [3].
> I
> > > > don't
> > > > > > think
> > > > > > > > > that
> > > > > > > > > >> it is critical because walk around exists.
> > > > > > > > > >>
> > > > > > > > > >> [1] https://issues.apache.org/jira/browse/IGNITE-2382
> > > > > > > > > >> [2] https://issues.apache.org/jira/browse/IGNITE-3136
> > > > > > > > > >> [3] https://issues.apache.org/jira/browse/IGNITE-2455
> > > > > > > > > >>
> > > > > > > > > >> On Fri, May 13, 2016 at 6:24 PM, Anton
Vinogradov <
> > > > > av@apache.org>
> > > > > > > > > wrote:
> > > > > > > > > >>
> > > > > > > > > >> > Igniters,
> > > > > > > > > >> >
> > > > > > > > > >> > We postponed code freeze till monday
UTC 19-00.
> > > > > > > > > >> >
> > > > > > > > > >> > On Thu, May 12, 2016 at 1:48 PM,
Anton Vinogradov <
> > > > > > av@apache.org>
> > > > > > > > > >> wrote:
> > > > > > > > > >> >
> > > > > > > > > >> > > Typo fix:
> > > > > > > > > >> > > Pushes to ignite-1.6 are allowed
till Friday (*May
> > *13)
> > > > > 19:00
> > > > > > UTC.
> > > > > > > > > >> > >
> > > > > > > > > >> > >
> > > > > > > > > >> > >
> > > > > > > > > >> > > On Thu, May 12, 2016 at 1:41
PM, Anton Vinogradov <
> > > > > > av@apache.org>
> > > > > > > > > >> wrote:
> > > > > > > > > >> > >
> > > > > > > > > >> > >> Igniters,
> > > > > > > > > >> > >>
> > > > > > > > > >> > >> Ignite 1.6 almost ready
to be finally tested.
> > > > > > > > > >> > >>
> > > > > > > > > >> > >> Branch ignite-1.6 now
contains all changes
> scheduled
> > > for
> > > > > 1.6.
> > > > > > > > > >> > >>
> > > > > > > > > >> > >> In case you want to add
something else to this
> > release,
> > > > > > please
> > > > > > > > note
> > > > > > > > > >> that
> > > > > > > > > >> > >> pushes to ignite-1.6 allowed
till Friday (Aug 13)
> > 19:00
> > > > > UTC.
> > > > > > > > > >> > >> After that date only fixes
will allowed.
> > > > > > > > > >> > >>
> > > > > > > > > >> > >> On Fri, May 6, 2016 at
4:18 PM, Anton Vinogradov <
> > > > > > av@apache.org>
> > > > > > > > > >> wrote:
> > > > > > > > > >> > >>
> > > > > > > > > >> > >>> Igniters,
> > > > > > > > > >> > >>>
> > > > > > > > > >> > >>> We're going to release
Ignite 1.6 in the nearest
> > > future.
> > > > > > > > > >> > >>> Branch ignite-1.6
was created and already contains
> > > > changes
> > > > > > > > > scheduled
> > > > > > > > > >> > for
> > > > > > > > > >> > >>> 1.6.
> > > > > > > > > >> > >>>
> > > > > > > > > >> > >>> And from now on, I
propose to start testing and
> > fixing
> > > > > > > > ignite-1.6
> > > > > > > > > >> > source
> > > > > > > > > >> > >>> code to provide stable
release.
> > > > > > > > > >> > >>>
> > > > > > > > > >> > >>> As you know we have
a huge amount of tests and
> some
> > of
> > > > > them
> > > > > > now
> > > > > > > > > >> failing
> > > > > > > > > >> > >>> at release branch.
> > > > > > > > > >> > >>> Fails can be found
here:
> > > > > > > > > >> > >>>
> > > > > > > > > >> > >>>
> > > > > > > > > >> >
> > > > > > > > > >>
> > > > > > > > >
> > > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> http://149.202.210.143:8111/project.html?projectId=IgniteTests&tab=projectOverview&branch_IgniteTests=ignite-1.6
> > > > > > > > > >> > >>>
> > > > > > > > > >> > >>> So, feel free to start
investigations and fix
> issues
> > > :)
> > > > > > > > > >> > >>>
> > > > > > > > > >> > >>
> > > > > > > > > >> > >>
> > > > > > > > > >> > >
> > > > > > > > > >> >
> > > > > > > > > >>
> > > > > > > > > >>
> > > > > > > > > >>
> > > > > > > > > >> --
> > > > > > > > > >> Andrey Gura
> > > > > > > > > >> GridGain Systems, Inc.
> > > > > > > > > >> www.gridgain.com
> > > > > > > > > >>
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > --
> > > > > > > > Sergey Kozlov
> > > > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > > >
> > > > --
> > > > Alexey Kuznetsov
> > > > GridGain Systems
> > > > www.gridgain.com
> > > >
> > >
> >
>

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