Re: Jackrabbit Oak 1.38.0 release plan

hi afaik the test class you refer to in the ticket summary was added in the light of OAK-9275. kind regards angela From: Julian Reschke Sent: Thursday, January 21, 2021 3:54 PM To: oak-dev@jackrabbit.apache.org Subject: Re: Jackrabbit Oak 1.38.0 release plan

Re: Jackrabbit Oak 1.38.0 release plan

Am 21.01.2021 um 15:47 schrieb Angela Schreiber: hi julian so far i didn't manage to reproduce the test failure you describe in OAK-9324 and nor did i see it failing in the integration. so, not sure this should block the release given that it

Re: Jackrabbit Oak 1.38.0 release plan

hi julian so far i didn't manage to reproduce the test failure you describe in OAK-9324 and nor did i see it failing in the integration. so, not sure this should block the release given that it might be limited to windows. also note: the ticket

Re: Jackrabbit Oak 1.38.0 release plan

Am 21.01.2021 um 14:52 schrieb Andrei Dulceanu: Hi all, I'm planning to cut Jackrabbit Oak 1.38.0 tomorrow. I transitioned all open issues scheduled for 1.38.0 to 1.40.0: ... See : tests fail on Windows. I don't think we should release with

Jackrabbit Oak 1.38.0 release plan

Hi all, I'm planning to cut Jackrabbit Oak 1.38.0 tomorrow. I transitioned all open issues scheduled for 1.38.0 to 1.40.0: https://issues.apache.org/jira/issues/?jql=project%20%3D%20OAK%20AND%20fixVersion%20%3D%201.38.0%20%20AND%20resolution%20%3D%20Unresolved The candidate release notes are

Re: When to update the documentation

Thank you both for feedback. I guess I can reference the unreleased version, copying the value form the JIRA issue field "Fix Versions/s"? On Thu, Jan 21, 2021 at 9:57 AM Angela Schreiber wrote: > hi > > same here... for new features i usually refer to jira or the released > version to

Re: When to update the documentation

hi same here... for new features i usually refer to jira or the released version to clarify that it's not available in older versions. if i remember correctly we discussed this in the past. afaik the conclusion was back then that the documentation should reflect the latest trunk as we don't

Re: When to update the documentation

Hi Miroslav, I always included any documentation updates in the same commit introducing the change. I guess it's more transparent and this way one makes sure not to forget about it later. Regards, Andrei On Wed, Jan 20, 2021 at 1:13 PM Miroslav Smiljanic wrote: > Hi All, > > I have created an