Re: Oak 1.5.5 release plan

[Davide Giannella <da...@apache.org>]

On 30/06/2016 10:29, Davide Giannella wrote:
> Hello team,
>
> I'm planning to cut Oak 1.5.5 on Monday 4th July morning BST.
>
> If there are any objections please let me know. Otherwise I will
> re-schedule any non-resolved issue for the next iteration.
>
>

I've been trying to release 1.5.5 but
https://issues.apache.org/jira/browse/OAK-3753 is constantly failing on
my side. I've reopened and made a blocker for the release.

Still trying yet one more round to see if it's just misfortune or not.
Weird as it's been closed as "cannot reproduce" before 1.4.0....

Cheers
Davide

Re: Oak 1.5.5 release plan

[Alex Parvulescu <al...@gmail.com>]

I don't see any changes that might have introduced this recently, so I
think you can go ahead with the release, and we can look into the failure
in parallel.

best,
alex


On Mon, Jul 4, 2016 at 1:04 PM, Davide Giannella <da...@apache.org> wrote:

> On 04/07/2016 11:19, Davide Giannella wrote:
> >
> > I've been trying to release 1.5.5 but
> > https://issues.apache.org/jira/browse/OAK-3753 is constantly failing on
> > my side. I've reopened and made a blocker for the release.
> >
> > Still trying yet one more round to see if it's just misfortune or not.
> > Weird as it's been closed as "cannot reproduce" before 1.4.0....
> >
> >
>
> Tried to run it one more time and it passed. It failed 3 times in a row
> and then succeeded. How would we like to proceed? Shall I release anyhow
> or do we want to wait for a deeper investigation of the issue?
>
> Please mind that this is trunk, it's considered unstable and we've been
> having this issue since before 1.4.0. I'm for proceeding.
>
> Davide
>
>
>

Re: Oak 1.5.5 release plan

[Davide Giannella <da...@apache.org>]

On 04/07/2016 11:19, Davide Giannella wrote:
>
> I've been trying to release 1.5.5 but
> https://issues.apache.org/jira/browse/OAK-3753 is constantly failing on
> my side. I've reopened and made a blocker for the release.
>
> Still trying yet one more round to see if it's just misfortune or not.
> Weird as it's been closed as "cannot reproduce" before 1.4.0....
>
>

Tried to run it one more time and it passed. It failed 3 times in a row
and then succeeded. How would we like to proceed? Shall I release anyhow
or do we want to wait for a deeper investigation of the issue?

Please mind that this is trunk, it's considered unstable and we've been
having this issue since before 1.4.0. I'm for proceeding.

Davide