Mailing-List: contact dev-help@ignite.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ignite.apache.org
MIME-Version: 1.0
In-Reply-To: <20160809183731.GR18734@boudnik.org>
References: <20160809183731.GR18734@boudnik.org>
From: Pavel Tupitsyn <ptupitsyn@apache.org>
Date: Wed, 10 Aug 2016 12:26:05 +0300
Message-ID: <CAK2_iMO8amc2YvkXF3FWTZsgAPJbLxK=fYmp+7w2bTjxbNEdzA@mail.gmail.com>
Subject: Re: Release notes preparations...
To: dev@ignite.apache.org
Content-Type: multipart/alternative; boundary=001a113d3806e16de30539b43e21
archived-at: Wed, 10 Aug 2016 09:26:38 -0000

--001a113d3806e16de30539b43e21
Content-Type: text/plain; charset=UTF-8

Cos, you are right.

More than 300 (!) tickets has been moved to 1.8 yesterday when I released
1.7 version in JIRA.

For what it's worth, I've added a step to vote verification:
https://cwiki.apache.org/confluence/display/IGNITE/Release+Process

Pavel

On Tue, Aug 9, 2016 at 9:37 PM, Konstantin Boudnik <cos@apache.org> wrote:

> Gents,
>
> this has triggered the recollection of the release notes conversation we
> had
> the other day. Looks like the ticket queue isn't getting pruned in time of
> the
> release, so the changes like that are happening postfactum. This is either
> leads to more load on the RM, or might be error-prone.
>
> I want to share some of the RM best practices that I have observed and used
> myself in other projects (Bigtop, Hadoop, etc.). JIRA cleaning/pruning is
> normally one of the steps _leading_ to release. It helps to narrow down the
> scope of the work that still is needed to be done before the release could
> be
> cut. Once the scope is decided and all JIRAs considered for later are
> moved to
> the consequent release, JIRA software allow you to generate the release
> notes
> file, that can be included into the release itself. This provide a
> necessary
> connection between the source code in the release and the issues addressed
> by
> it. Once the release is published, the RM needs to officially _release_ the
> version in the JIRA software. At this point, the number of unfinished
> ticket
> against that version should be exactly 0. It is just a matter of the
> house-keeping and a good engineering practice. And it helps to keep down
> the
> amount of the mess.
>
> Hope it makes sense.
>   Cos
>
> ----- Forwarded message from "Pavel Tupitsyn (JIRA)" <jira@apache.org>
> -----
>
> Date: Tue, 9 Aug 2016 12:32:32 +0000 (UTC)
> From: "Pavel Tupitsyn (JIRA)" <jira@apache.org>
> To: cos@apache.org
> Subject: [jira] [Updated] (IGNITE-2437) Zeppelin interperet doesn't import
> external dependencies
>
>
>      [ https://issues.apache.org/jira/browse/IGNITE-2437?page=
> com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
>
> Pavel Tupitsyn updated IGNITE-2437:
> -----------------------------------
>     Fix Version/s:     (was: 1.7)
>                    1.8
>
> > Zeppelin interperet doesn't import external dependencies
> > --------------------------------------------------------
> >
> >                 Key: IGNITE-2437
> >                 URL: https://issues.apache.org/jira/browse/IGNITE-2437
> >             Project: Ignite
> >          Issue Type: Bug
> >          Components: general
> >    Affects Versions: 1.5.0.final
> >         Environment: zeppelin 0.5.5
> > ignite 1.5.0.final
> >            Reporter: Konstantin Boudnik
> >            Assignee: Andrey Gura
> >             Fix For: 1.8
> >
> >
> > After configuring Ignite's interpreter for Zeppelin, tried to run the
> following
> > {code}
> > %dep
> > z.load("/usr/lib/ignite/libs/ignite-cache-objects.jar")
> > %ignite
> > import io.company._
> > console>:23: error: object company is not a member of package io
> >        import io.company._
> > {code}
> > same code works just fine in spark interpreter though.
>
>
>
> --
> This message was sent by Atlassian JIRA
> (v6.3.4#6332)
>
> ----- End forwarded message -----
>

--001a113d3806e16de30539b43e21--