The Apache Jenkins build system has built Apache Jackrabbit Oak matrix (build
#329)
Status: Still Failing
Check console output at
https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/329/ to view
the results.
+1
On 13/08/15 14:15, "Marcel Reutegger" wrote:
>I'd leave it at the date the release was cut. this makes it
>possible to roughly judge whether a commit made it into the
>release or not.
On 13/08/15 13:58, "Davide Giannella" wrote:
>On 13/08/2015 10:17, Stefan Egli wrote:
>> I¹d find it more useful (for us) when it would be the cut-date.
>>
>It's always the cut date in the beginning. Shall we change it then to
>the actual release date once it's announced or leave it to the cut date
Actual release data would be great to map planing dependencies properly.
On 13/08/15 13:58, "Davide Giannella" wrote:
>On 13/08/2015 10:17, Stefan Egli wrote:
>> I¹d find it more useful (for us) when it would be the cut-date.
>>
>It's always the cut date in the beginning. Shall we change it th
+1
On 13/08/15 10:17, "Stefan Egli" wrote:
>I¹d find it more useful (for us) when it would be the cut-date.
>
>Cheers,
>Stefan
>
>On 13/08/15 10:08, "Davide Giannella" wrote:
>
>>Hello team,
>>
>>a trivia question about release dates.
>>
>>Normally in jira I set the release date on a future
On 13/08/2015 10:17, Stefan Egli wrote:
> I¹d find it more useful (for us) when it would be the cut-date.
>
It's always the cut date in the beginning. Shall we change it then to
the actual release date once it's announced or leave it to the cut date? :)
Davide
I¹d find it more useful (for us) when it would be the cut-date.
Cheers,
Stefan
On 13/08/15 10:08, "Davide Giannella" wrote:
>Hello team,
>
>a trivia question about release dates.
>
>Normally in jira I set the release date on a future release for when we
>plan to cut it. But we have the voting p
Hello team,
a trivia question about release dates.
Normally in jira I set the release date on a future release for when we
plan to cut it. But we have the voting process of 72hrs that means the
actual release date will be 3 days after the cut.
Shall we put on jira then the release date as the ac
Good point, done in http://svn.apache.org/r1695655
Cheers,
Stefan
On 13/08/15 09:35, "Davide Giannella" wrote:
>On 12/08/2015 14:32, stefane...@apache.org wrote:
>> Author: stefanegli
>> Date: Wed Aug 12 12:32:35 2015
>> New Revision: 1695492
>>
>> URL: http://svn.apache.org/r1695492
>> Log:
>>
On 12/08/2015 14:32, stefane...@apache.org wrote:
> Author: stefanegli
> Date: Wed Aug 12 12:32:35 2015
> New Revision: 1695492
>
> URL: http://svn.apache.org/r1695492
> Log:
> OAK-2682 : Introducing time difference detection for DocumentNodeStore: now
> startup will fail if oak and mongo server a
10 matches
Mail list logo