Re: Intent to backport to 1.10: OAK-8018

On 05.12.2019 16:03, Angela Schreiber wrote: Hi Julian But why do we have to align Oak 1.10 with trunk now that we have stable release on regular basis instead of releasing only once a year? (see other thread) IMO it would be better and a lot less risky to push for updating to a more recent

Re: Intent to backport to 1.10: OAK-8018

porting the huge number of API changes we made over the last couple of years. Kind regards Angela From: Julian Reschke Sent: Thursday, December 5, 2019 2:38 PM To: oak-dev@jackrabbit.apache.org ; Angela Schreiber Subject: Re: Intent to backport to 1.10: OAK

Re: Intent to backport to 1.10: OAK-8018

On 05.12.2019 13:51, Angela Schreiber wrote: Hi Julian This changes with OAK-8018 modified public API as far as I can see and I vaguely remember that we concluded in the past that we want to avoid back porting anything that is not a critical bug and be particularly careful not to back port

Re: Intent to backport to 1.10: OAK-8018

19 1:34 PM To: oak-dev@jackrabbit.apache.org Subject: Intent to backport to 1.10: OAK-8018 <https://issues.apache.org/jira/browse/OAK-8018>: "Move LazyValue from oak-core to oak-commons" See also previous message "Deprecating API signatures referring to Guava in 1.10" (&

Intent to backport to 1.10: OAK-8018

: "Move LazyValue from oak-core to oak-commons" See also previous message "Deprecating API signatures referring to Guava in 1.10"