Mailing-List: contact dev-help@apex.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@apex.incubator.apache.org
MIME-Version: 1.0
In-Reply-To: <56C1FEC2.9060904@datatorrent.com>
References: 
 <CAKJfLDPEN5D+1vd578c43hoaqsFhfP-fc1Rm==UW_OessQVdsA@mail.gmail.com>
	<CAA7LveFJxNEFnkgpt4KjzJNzNzxAQaZKiPLExzMvAGCQs_f5ig@mail.gmail.com>
	<CAHekGF8ZNBp7CoTpVHiZyXfURthv=CD6QmWpywHXhMRD4BSr_g@mail.gmail.com>
	<CAKJfLDMDyvNggxs86BKYHGm-hFnz8H4np9z6V97DuV8RdaqH5A@mail.gmail.com>
	<CAHekGF92c2Yqakr0U6ozNDkQ9nOETwnJ9LKjQFKitYmoi_dz9w@mail.gmail.com>
	<56C1FEC2.9060904@datatorrent.com>
Date: Wed, 17 Feb 2016 20:55:40 -0800
Message-ID: 
 <CAKJfLDP8cUWHiXmEbRZs3Sd8fR-Ry98fBTZVhEQcrmXXcWUimQ@mail.gmail.com>
Subject: Re: Malhar 3.3.1 patch release
From: Thomas Weise <thomas@datatorrent.com>
To: dev@apex.incubator.apache.org
Content-Type: multipart/alternative; boundary=001a113ce5689e12c5052c042df2

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

Here are some more:

https://issues.apache.org/jira/browse/APEXMALHAR-1973
https://issues.apache.org/jira/browse/APEXMALHAR-1970
https://issues.apache.org/jira/browse/APEXMALHAR-1984
https://issues.apache.org/jira/browse/APEXMALHAR-1983


On Mon, Feb 15, 2016 at 8:37 AM, Vlad Rozov <v.rozov@datatorrent.com> wrote:

> It will be good to send list of candidate JIRAs to be included into 3.3.1
> release for the community to vote on. Currently I see
>
> 1. APEXMALHAR-1993 Committed offsets are not present in offset manager
>    storage for kafka input operator
>    <https://issues.apache.org/jira/browse/APEXMALHAR-1993>
>
> 1. APEXMALHAR-1990 Occasional concurrent modification exceptions from
>    IdempotentStorageManager
>    <https://issues.apache.org/jira/browse/APEXMALHAR-1990>
>
>
> Is this a full list? Any other candidates?
>
> Vlad
>
>
> On 2/15/16 00:15, Yogi Devendra wrote:
>
>> I assume that this is backed by some user who need these fixes and not
>> ready to upgrade to apex core 3.3.0.
>>
>> +1 if above assumption is true.
>>
>> ~ Yogi
>>
>> On 14 February 2016 at 05:11, Thomas Weise <thomas@datatorrent.com>
>> wrote:
>>
>> That's correct, patch releases cannot upgrade dependencies to newer minor
>>> or major version.
>>>
>>> Also, these fixes should not force users to upgrade the Apex install.
>>>
>>> Thomas
>>>
>>> On Fri, Feb 12, 2016 at 8:04 PM, Yogi Devendra <yogidevendra@apache.org>
>>> wrote:
>>>
>>> Instead of patch release should we have next minor release which would
>>>>
>>> also
>>>
>>>> have dependency change to depend on apex-core-3.3.0?
>>>>
>>>> I guess dependency change can't go in the patch release. Is that
>>>> correct?
>>>>
>>>> ~ Yogi
>>>>
>>>> On 13 February 2016 at 08:04, Pramod Immaneni <pramod@datatorrent.com>
>>>> wrote:
>>>>
>>>> +1 for 3.3.1
>>>>>
>>>>> On Fri, Feb 12, 2016 at 5:50 PM, Thomas Weise <thomas@datatorrent.com>
>>>>> wrote:
>>>>>
>>>>> There are a few critical fixes to the Kafka operators and idempotency
>>>>>> support that might be good to provide as patch release? Perhaps there
>>>>>>
>>>>> are
>>>>
>>>>> other fixes in master that should go into it, too?
>>>>>>
>>>>>> Thomas
>>>>>>
>>>>>>
>

--001a113ce5689e12c5052c042df2--