You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-dev@jackrabbit.apache.org by Davide Giannella <da...@apache.org> on 2014/11/21 10:23:34 UTC
Oak 1.1.3 cut
Good morning team,
on next Monday around 2pm I will cut the next unstable release: 1.1.3.
There's still a bunch of unresolved issues. If you need more time just
ping me, we don't have to stick to precise date, otherwise you can wrap
it up for the 1.1.4 cut 2 weeks after (I've already created the version
in jira).
https://issues.apache.org/jira/issues/?jql=project%20%3D%20OAK%20AND%20fixVersion%20%3D%201.1.3%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20due%20ASC%2C%20priority%20DESC%2C%20created%20ASC
Cheers
Davide
Re: Oak 1.1.3 cut
Posted by Chetan Mehrotra <ch...@gmail.com>.
I have resolved mine issues. Work related to Lucene search enhancement
in current trunk is fine and a cut can be done. I have another patch
for custom analyzer but that would not break anything.
So from my side nothing pending for 1.1.3!
Chetan Mehrotra
On Mon, Dec 8, 2014 at 7:21 PM, Davide Giannella <da...@apache.org> wrote:
> Hello team,
>
> On 24/11/2014 11:22, Chetan Mehrotra wrote:
>> On Mon, Nov 24, 2014 at 4:36 PM, Davide Giannella <da...@apache.org> wrote:
>>> Yes of course. Just for my scheduling when roughly do you think we'll be
>>> in good shape for the cut?
>> Would be bit conservative here. Probably by next Monday it should be done!
>>
>> Chetan Mehrotra
>>
> didn't see any cut performed while I was away so I was thinking of
> cutting 1.1.3 tomorrow around 2pm GMT.
>
> there are still 4 issue unresolved for 1.1.3
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20OAK%20AND%20fixVersion%20%3D%201.1.3%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20due%20ASC%2C%20priority%20DESC%2C%20created%20ASC
>
> Can please the assignee let me know if more time is needed or move them
> 1.1.4?
>
> Anyone aware of any middle-commit that could badly break the
> functionality we should wait for before the cut?
>
> Cheers
> Davide
>
>
Re: Oak 1.1.3 cut
Posted by Davide Giannella <da...@apache.org>.
Hello team,
On 24/11/2014 11:22, Chetan Mehrotra wrote:
> On Mon, Nov 24, 2014 at 4:36 PM, Davide Giannella <da...@apache.org> wrote:
>> Yes of course. Just for my scheduling when roughly do you think we'll be
>> in good shape for the cut?
> Would be bit conservative here. Probably by next Monday it should be done!
>
> Chetan Mehrotra
>
didn't see any cut performed while I was away so I was thinking of
cutting 1.1.3 tomorrow around 2pm GMT.
there are still 4 issue unresolved for 1.1.3
https://issues.apache.org/jira/issues/?jql=project%20%3D%20OAK%20AND%20fixVersion%20%3D%201.1.3%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20due%20ASC%2C%20priority%20DESC%2C%20created%20ASC
Can please the assignee let me know if more time is needed or move them
1.1.4?
Anyone aware of any middle-commit that could badly break the
functionality we should wait for before the cut?
Cheers
Davide
Re: Oak 1.1.3 cut
Posted by Chetan Mehrotra <ch...@gmail.com>.
On Mon, Nov 24, 2014 at 4:36 PM, Davide Giannella <da...@apache.org> wrote:
> Yes of course. Just for my scheduling when roughly do you think we'll be
> in good shape for the cut?
Would be bit conservative here. Probably by next Monday it should be done!
Chetan Mehrotra
Re: Oak 1.1.3 cut
Posted by Davide Giannella <da...@apache.org>.
On 24/11/2014 09:18, Chetan Mehrotra wrote:
> Hi Davide,
>
> Looks like we would need to postphone the release as I am midway in
> the Lucene related changes (OAK-2268, OAK-2278) and I should be able
> to warp them up this week. Current oak-lucene code in trunk uses newer
> Lucene index (for fresh setups) and that currently does not handle all
> aggregation related changes
Yes of course. Just for my scheduling when roughly do you think we'll be
in good shape for the cut?
Cheers
Davide
Re: Oak 1.1.3 cut
Posted by Chetan Mehrotra <ch...@gmail.com>.
Hi Davide,
Looks like we would need to postphone the release as I am midway in
the Lucene related changes (OAK-2268, OAK-2278) and I should be able
to warp them up this week. Current oak-lucene code in trunk uses newer
Lucene index (for fresh setups) and that currently does not handle all
aggregation related changes
Would that work for you?
Chetan Mehrotra
On Mon, Nov 24, 2014 at 1:53 PM, Davide Giannella <da...@apache.org> wrote:
> Good morning team,
>
> friendly reminder that today 2.30pm GMT I will be cutting the next
> unstable release.
>
> Please double check for unresolved issues, wrap them up for the next
> release cycle if needed, and if you need more time don't hesitate in
> asking me directly.
>
> Cheers
> Davide
>
>
Re: Oak 1.1.3 cut
Posted by Davide Giannella <da...@apache.org>.
Good morning team,
friendly reminder that today 2.30pm GMT I will be cutting the next
unstable release.
Please double check for unresolved issues, wrap them up for the next
release cycle if needed, and if you need more time don't hesitate in
asking me directly.
Cheers
Davide