On 06/04/2016 15:25, Francesco Mari wrote:
> I was talking about trunk, of course. Developers working in areas where
> backports are the norm have to carefully consider if and when using Java 7
> language features would be appropriate. New portions of the codebase could
> use of the new features fr
Language features would be available for new, backport-free developments.
Existing code doesn't have to use those features if they would be an issue
during backports.
2016-04-07 10:25 GMT+02:00 Davide Giannella :
> On 06/04/2016 15:25, Francesco Mari wrote:
> > I was talking about trunk, of cours
Hello team,
I'm planning to cut Oak 1.5.1 on Monday 11th April in the morning CEST.
If there are any objections please let me know. Otherwise I will
re-schedule any non-resolved issue for the next iteration.
Thanks
Davide
Hi Tomek
While I see that OAK-4128 has been resolved fixed, I still experience
a failing SegmentToJdbcTest.validateMigration test, with my pending
changes for OAK-4119.
I will take the liberty to mark the test with an @Ignore tag when
committing my changes. What's your preferred way to investigat
Hello Angela,
> On 07 Apr 2016, at 13:37, Angela Schreiber wrote:
>
> I will take the liberty to mark the test with an @Ignore tag when
> committing my changes. What's your preferred way to investigate
> this? Shall I clone the OAK-4119? Or do you want to take a closer
> look once I am done such
Hi Tomek
I create https://issues.apache.org/jira/browse/OAK-4174
in order not to mix my modifications with the upgrade
code as i consider the @ignore mark just a temp workaround
in order to keep everyone and jenkins happy :-)
kind regards
angela
On 07/04/16 14:01, "Tomek Rekawek" wrote:
>Hello
Hi Domenic,
My POV:
You are essentially testing how fast Oak or JR can put nodes into
MySQL/Postgres/Mongo. IMO Oak’s design does not suggest that there should be
fundamental differences between JR and Oak for this isolated case. (*)
However, where Oak is expected to outperform JR is when
1) th
We could enforce java6 signatures for the branches using the
animal-sniffer-maven-plugin. This should help detect bogus backports
quickly.
Regards
Julian
On Thu, Apr 7, 2016 at 10:57 AM, Francesco Mari
wrote:
> Language features would be available for new, backport-free developments.
> Existing
