Hi Geode Developers,
>From the discussion in this email thread we are waiting on couple of GEODE
JIRAs to be resolved to continue with 1.7.0 release process.
GEODE-5615 - resolved.
GEODE-5601 - In-progress [DanSmith / Kenneth Howe ]
GEODE-5594 - Open [Sai Boorlagadda]
GEODE-5338 - Open [Sai Boorlagadda]
GEODE-5619 - Resolved
Once these tickets are marked resolved we will start with the 1.7.0 release
process.
Also, all tickets marked as closed or resolved as 1.8.0 fix version have
been marked as 1.7.0. Please continue using the fix version as 1.7.0 till
we send out an email regarding the creation of the new release branch.
Below tickets were changed from 1.8.0 to 1.7.0
GEODE-5627
GEODE-5583
GEODE-5582
GEODE-5575
GEODE-5554
GEODE-5549
GEODE-5530
GEODE-5528
GEODE-5520
GEODE-5510
GEODE-5503
GEODE-5499
GEODE-5495
GEODE-5493
GEODE-5489
GEODE-5488
GEODE-5480
GEODE-5477
GEODE-5473
GEODE-5471
GEODE-5470
GEODE-5461
GEODE-5460
GEODE-5453
GEODE-5447
GEODE-5439
GEODE-5438
GEODE-5436
GEODE-5435
GEODE-5432
GEODE-5426
GEODE-5420
GEODE-5416
GEODE-5408
GEODE-5387
GEODE-5383
GEODE-5376
GEODE-5371
GEODE-5363
GEODE-5361
GEODE-5360
GEODE-5360
GEODE-5351
GEODE-5350
GEODE-5349
GEODE-5333
GEODE-5330
GEODE-5325
GEODE-5323
GEODE-5320
GEODE-5319
GEODE-5317
GEODE-5312
GEODE-5311
GEODE-5310
GEODE-5307
GEODE-5306
GEODE-5305
GEODE-5302
GEODE-5300
GEODE-5298
GEODE-5296
GEODE-5292
GEODE-5290
GEODE-5287
GEODE-5283
GEODE-5281
GEODE-5278
GEODE-5277
GEODE-5276
GEODE-5274
GEODE-5273
GEODE-5272
GEODE-5270
GEODE-5269
GEODE-5267
GEODE-5265
GEODE-5255
GEODE-5249
GEODE-5237
GEODE-5223
GEODE-5220
GEODE-5186
GEODE-5157
GEODE-4965
GEODE-4791
GEODE-4726
GEODE-4614
GEODE-4593
GEODE-4336
GEODE-3530
GEODE-3505
GEODE-1866
GEODE-1357
On Mon, Aug 27, 2018 at 12:11 PM Nabarun Nag <n...@apache.org> wrote:
> @Bruce those changes were done when 1.7.0 release process was in-progress,
> and a release branch was already created. But we stopped that process mid
> way. This happened in May 2018.
> We are planning to rebase the 1.7.0 brach with the current develop pretty
> soon.
>
> Regards
> Nabarun
>
> On Mon, Aug 27, 2018 at 12:02 PM Bruce Schuchardt <bschucha...@pivotal.io>
> wrote:
>
>> It looks like we've cut a 1.7.0 release branch that says its 1.8.0. Is
>> that intentional?
>>
>>
>> private static final byte GEODE_180_ORDINAL =95;
>>
>> public static final VersionGEODE_180 =
>> new Version("GEODE","1.8.0", (byte)1, (byte)8, (byte)0,
>> (byte)0,GEODE_180_ORDINAL);
>>
>>
>> On 8/27/18 9:50 AM, Sai Boorlagadda wrote:
>> > After reading through the weekend, validating against CN as a
>> > fallback should be acceptable and dont have any further concerns
>> > with default JDK's implementation as expressed[1].
>> >
>> > Planning to merge GEODE-5594 today and following with GEODE-5338.
>> >
>> > Sai
>> > [1]
>> >
>> https://lists.apache.org/thread.html/906540e18fa6f85fc77c88c28fc74a61402471d2eed4ee9dab4813c9@%3Cdev.geode.apache.org%3E
>> >
>> > On Fri, Aug 24, 2018 at 5:07 PM Sai Boorlagadda <
>> sai.boorlaga...@gmail.com>
>> > wrote:
>> >
>> >> Regarding GEODE-5594, though the current implementation is good and
>> needed
>> >> more coverage.
>> >>
>> >> While adding tests to cover negative cases, I found something about
>> JDK's
>> >> default implementation of
>> >> hostname validation which I am not happy about and so it needs a
>> >> rethought. It could result in
>> >> implementing our own custom algorithm to do hostname validation.
>> >>
>> >> I will send out details and seek to advise on what we should do in a
>> >> different thread.
>> >>
>> >> Sai
>> >>
>> >> On Fri, Aug 24, 2018 at 10:52 AM Alexander Murmann <
>> amurm...@pivotal.io>
>> >> wrote:
>> >>
>> >>> To summarize where we are right now in this discussion, I see the
>> >>> following
>> >>> tickets listed in this thread as want-to-haves for 1.7:
>> >>>
>> >>> - GEODE-5615 - ✅ resolved
>> >>> - GEODE-5601 - 🏃♀️ in progress
>> >>> - GEODE-5594 - 🏃♀️ waiting for PR review
>> >>> - GEODE-5338 - 🏃♀️ waiting for PR review
>> >>> - GEODE-5619 - 🙄 in progress in JIRA but has merged PR. What
>> does it
>> >>> mean?
>> >>>
>> >>> Is there anything else that needs to go into 1.7?
>> >>>
>> >>> It seems like the best we all can do is to review Sai's PRs. Is that
>> >>> correct?
>> >>>
>> >>> On Wed, Aug 22, 2018 at 10:59 AM, Jens Deppe <jde...@pivotal.io>
>> wrote:
>> >>>
>> >>>> I'd also like to include GEODE-5619
>> >>>>
>> >>>> On Tue, Aug 21, 2018 at 3:59 PM Xiaojian Zhou <gz...@pivotal.io>
>> wrote:
>> >>>>
>> >>>>> +1
>> >>>>>
>> >>>>> The release will be a great one with so many historical bugs fixed.
>> >>>>>
>> >>>>> Today I tried to use IJ to build and run with latest build.gradle
>> and
>> >>>>> recent moved test packages, it worked. So this refactoring is also
>> >>>> success.
>> >>>>> On Tue, Aug 21, 2018 at 3:52 PM, Anthony Baker <aba...@pivotal.io>
>> >>>> wrote:
>> >>>>>> I most definitely agree!
>> >>>>>>
>> >>>>>> Anthony
>> >>>>>>
>> >>>>>>
>> >>>>>>> On Aug 21, 2018, at 2:26 PM, Dan Smith <dsm...@pivotal.io> wrote:
>> >>>>>>>
>> >>>>>>> I think we do want to wait for GEODE-5615 (DistributedTest OOMEs)
>> >>> and
>> >>>>>>> GEODE-5601 (AcceptanceTest port conflicts) to be fixed before
>> >>> cutting
>> >>>>> the
>> >>>>>>> new 1.7 branch. It would be better if we don't create a release
>> >>>> branch
>> >>>>>> from
>> >>>>>>> a point where we have these systematic issues with our pipeline.
>> >>>>>>>
>> >>>>>>> -Dan
>> >>>>>>
>>
>>
