On 2017-06-01 11:13, Amit Jain wrote:
Ok. Maybe this time we create a 2.14.2 release in 4-5 weeks time?
OK.
(You may have to remind me though :-)
Ok. Maybe this time we create a 2.14.2 release in 4-5 weeks time?
On Thu, Jun 1, 2017 at 2:37 PM, Julian Reschke
wrote:
> On 2017-06-01 10:53, Amit Jain wrote:
>
>> On Thu, Jun 1, 2017 at 2:12 PM, Julian Reschke
>> wrote:
>>
>> Now when do we need
On 2017-06-01 10:53, Amit Jain wrote:
On Thu, Jun 1, 2017 at 2:12 PM, Julian Reschke
wrote:
Now when do we need that in a 2.14 release?
I think we can follow the normal schedule (monthly?)
Thanks
Amit
I currently do one Jackrabbit release per month (unless
On Thu, Jun 1, 2017 at 2:12 PM, Julian Reschke
wrote:
> Now when do we need that in a 2.14 release?
>
I think we can follow the normal schedule (monthly?)
Thanks
Amit
On 2017-06-01 08:32, Amit Jain wrote:
On Wed, May 31, 2017 at 4:36 PM, Julian Reschke
wrote:
I can do the backport if you want
Sure.
Done (JCR-4115).
Now when do we need that in a 2.14 release?
Best regards, Julian
On Wed, May 31, 2017 at 4:36 PM, Julian Reschke
wrote:
> I can do the backport if you want
Sure.
On 2017-05-31 12:37, Amit Jain wrote:
Yes, I meant to ask if we should start backporting as update in Oak would
be delayed.
...
+1 (I can do the backport if you want)
Yes, I meant to ask if we should start backporting as update in Oak would
be delayed.
On Wed, May 31, 2017 at 3:51 PM, Julian Reschke
wrote:
> On 2017-05-31 12:13, Amit Jain wrote:
>
>> Hi Team,
>>
>> Cross posting on both the Jackrabbit & Oak lists.
>>
>> A while back we
Hi Team,
Cross posting on both the Jackrabbit & Oak lists.
A while back we changed the DataStore to use SHA-256 to generate the ids.
What should be done for the backports?
Thanks
Amit