reef-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dongjoon Hyun (JIRA)" <>
Subject [jira] [Commented] (REEF-113) Integrate .NET API documentation with our website
Date Mon, 01 Feb 2016 05:21:39 GMT


Dongjoon Hyun commented on REEF-113:

Oh, right. Next release manager is [~yunseong]. I made a mistake for that. For the website
update policy, it's not changed. I'm sure you're right.

But, IMHO, for this one, I thought the content of this .Net document should match with 0.14.
There is two reasons.

First, we publish APIs with the release. As you see, there is no document for 0.14-snapshot.
We have only latest docs for 0.13 release.

Second, if we want to publish 0.13 .Net API, we should do that in 0.13 branch (not master.).
It's possible, but we need to cherry-pick a lot commits (specially, REEF-1135 changing all
.Net license headers) and do that for old sources. But, in these days, .Net API changes a
lot, so it doesn't seem to be so necessary.

I think this issue is a big change. It would be better for first .Net API docs to go together
with our first TLP release (0.14).

It's just my opinion. How do you think about that, [~markus.weimer] and [~MariiaMykhailova]?

> Integrate .NET API documentation with our website
> -------------------------------------------------
>                 Key: REEF-113
>                 URL:
>             Project: REEF
>          Issue Type: Improvement
>          Components: REEF.NET, Website
>            Reporter: Markus Weimer
>            Assignee: Mariia Mykhailova
>             Fix For: 0.14
> The REEF website today lists the API documentation for our Java code. We should integrate
the API documentation for the .NET code as well.

This message was sent by Atlassian JIRA

View raw message