-
Story
-
Resolution: Done
-
Medium
The API doc issue is whether we use tools to generate OSC API documentation.
If any project (repo) will have API docs in futrure releaes, please contact me <niweichen@chinamobile.com> (make sure send me your time zone) before Monday 9^th^ Mar. I will arrange a friendly time for participants and have a discussion about it.
# | Subject | Branch | Project | Status | CR | V |
---|---|---|---|---|---|---|
3118,7 | API documentation | master | nonrtric | Status: MERGED | +2 | +1 |
3129,4 | Change name of policy ID in API | master | nonrtric | Status: MERGED | +2 | +1 |
3132,1 | Change name of policy ID in API | master | portal/nonrtric-controlpanel | Status: MERGED | +2 | +1 |
3164,3 | Improved error printouts | master | portal/nonrtric-controlpanel | Status: MERGED | +2 | +1 |
3263,1 | Add Non-RT RIC documentation | master | doc | Status: ABANDONED | 0 | 0 |
3268,2 | Add copyright to documentation | master | portal/nonrtric-controlpanel | Status: MERGED | +2 | +1 |
3289,3 | Add Non-RT RIC documentation | master | doc | Status: MERGED | +2 | +1 |
3290,1 | Add links to new API documentation | master | nonrtric | Status: MERGED | +2 | +1 |
3345,1 | Bugfix, handling of empty types | master | portal/nonrtric-controlpanel | Status: MERGED | +2 | +1 |