If it is a known issue which is yet to be fixed (and not a
regression), then it is fine - since we had it earlier as well I
guess.
Given that, I am +1 on release; though it would be nice to get it
resolved given the mismatch in release artifacts.

Thanks,
Mridul

On Tue, May 23, 2017 at 12:38 PM, Ted Yu <yuzhih...@gmail.com> wrote:
> I suggest getting BAHIR-88
> <https://issues.apache.org/jira/browse/BAHIR-88> fixed
> - this may affect future release(s).
>
> On Tue, May 23, 2017 at 12:29 PM, Luciano Resende <luckbr1...@gmail.com>
> wrote:
>
>> The issue reported was for Spark extensions
>> https://issues.apache.org/jira/browse/BAHIR-88
>>
>>
>> And I guess it is also applicable for Flink extensions
>>
>>
>> But the issue is still open.
>>
>>
>> On Tue, May 23, 2017 at 12:08 PM, Mridul Muralidharan <
>> mridul...@apache.org>
>> wrote:
>>
>> > Hi Luciano,
>> >
>> >   I would not consider them blocking - but I wanted clarity about
>> > them, since I had seen jira's to the effect that they were fixed ?
>> > Not sure if I am misremembering !
>> >
>> > Regards,
>> > Mridul
>> >
>> >
>> > On Tue, May 23, 2017 at 12:01 PM, Luciano Resende <luckbr1...@gmail.com>
>> > wrote:
>> > > On Sun, May 21, 2017 at 11:50 PM, Mridul Muralidharan <
>> > mridul...@apache.org>
>> > > wrote:
>> > >
>> > >> Hi,
>> > >>
>> > >>   From the release tag, clean build and tests work fine, signatures
>> > match.
>> > >>
>> > >> The source at https://dist.apache.org/repos/
>> > dist/dev/bahir/bahir-flink/1.
>> > >> 0-rc5/
>> > >> has additional files which are not in repo:
>> > >>
>> > >> Not in repo ./distribution/pom.xml.releaseBackup
>> > >> Not in repo ./flink-connector-activemq/pom.xml.releaseBackup
>> > >> Not in repo ./flink-connector-akka/pom.xml.releaseBackup
>> > >> Not in repo ./flink-connector-flume/pom.xml.releaseBackup
>> > >> Not in repo ./flink-connector-netty/pom.xml.releaseBackup
>> > >> Not in repo ./flink-connector-redis/pom.xml.releaseBackup
>> > >> Not in repo ./pom.xml.releaseBackup
>> > >> Not in repo ./release.properties
>> > >>
>> > >> I thought this was fixed, but I could be remembering wrong ?
>> > >>
>> > >>
>> > >>
>> > > That's what I thought as well, but it might have been for the Spark
>> > > release.
>> > >
>> > > Are you  considering this blocking ? Or would it be ok to continue with
>> > the
>> > > approval of the release ?
>> > >
>> > > --
>> > > Luciano Resende
>> > > http://twitter.com/lresende1975
>> > > http://lresende.blogspot.com/
>> >
>>
>>
>>
>> --
>> Luciano Resende
>> http://twitter.com/lresende1975
>> http://lresende.blogspot.com/
>>

Reply via email to