hi chetan
On 24/03/17 07:11, "Chetan Mehrotra" wrote:
>On Thu, Mar 23, 2017 at 10:19 PM, Angela Schreiber
>wrote:
>> i have been working on should already
>> be included in the documentation because i try to do that before i
>>resolve
>> the
On Thu, Mar 23, 2017 at 10:19 PM, Angela Schreiber wrote:
> i have been working on should already
> be included in the documentation because i try to do that before i resolve
> the issue.
Thats much better! What we can do is mark such new stuff with `@since
Oak 1.6` and then
and maybe i have to add: the things i have been working on should already
be included in the documentation because i try to do that before i resolve
the issue.
so my comment refers to what i would expect to be linked on the main...
not sure how your suggestion below would be covered by stuff
Hi Chetan,
I created OAK-5977 [0] for S3DataStore changes as a subtask. Perhaps it
should be assigned to Amit Jain who probably has the best understanding of
all the S3DataStore changes in 1.6.
[0] - https://issues.apache.org/jira/browse/OAK-5977
-MR
On Thu, Mar 23, 2017 at 8:15 AM, Chetan
hi chetan
wouldn't it make more sense to generated list directly from JIRA? after
all that's exactly i would do to make sure i have a comprehensive list of
improvements and new features i was working on between oak 1.4 and 1.6.
kind regards
angela
On 23/03/17 15:15, "Chetan Mehrotra"
Hi Team,
As part of OAK-5976 I am trying to collect topics around various
enhancements done in Oak 1.6 release which we should document and make
end user aware of them and take benefit of.
For now I have covered various topics in Indexing, Document NodeStore
new features, Observation etc.