Skip to content

Public Release r1.2 for ModelAsAService APIs (Fall25 M4)#18

Merged
lihaojie-CMCC merged 39 commits intomainfrom
lihaojie-CMCC-patch-1
Sep 18, 2025
Merged

Public Release r1.2 for ModelAsAService APIs (Fall25 M4)#18
lihaojie-CMCC merged 39 commits intomainfrom
lihaojie-CMCC-patch-1

Conversation

@lihaojie-CMCC
Copy link
Contributor

What type of PR is this?

Add one of the following kinds:

  • subproject management

What this PR does / why we need it:

Create the initial public release of Model As A Service APIs to be included in Fall25 Meta release.

Which issue(s) this PR fixes:

Fixes #

@github-actions
Copy link

github-actions bot commented Aug 26, 2025

🦙 MegaLinter status: ✅ SUCCESS

Descriptor Linter Files Fixed Errors Elapsed time
✅ ACTION actionlint 2 0 0.01s
✅ API spectral 3 0 4.04s
✅ GHERKIN gherkin-lint 3 0 1.04s
✅ REPOSITORY git_diff yes no 0.0s
✅ REPOSITORY secretlint yes no 0.66s
✅ YAML yamllint 3 0 0.59s

See detailed report in MegaLinter reports

MegaLinter is graciously provided by OX Security

@lihaojie-CMCC
Copy link
Contributor Author

Work in Progress

@lihaojie-CMCC lihaojie-CMCC requested a review from a team August 27, 2025 06:21
@hdamker
Copy link
Contributor

hdamker commented Aug 27, 2025

@lihaojie-CMCC Please merge the main branch into the PR branch and resolve the merge conflicts. If done mark it again as "Ready for review".

@hdamker hdamker marked this pull request as draft August 27, 2025 06:41
@lihaojie-CMCC lihaojie-CMCC changed the title Public Release r1.1 for ModelAsAService APIs (Fall25 M4) Public Release r1.2 for ModelAsAService APIs (Fall25 M4) Aug 28, 2025
@lihaojie-CMCC lihaojie-CMCC marked this pull request as ready for review August 28, 2025 12:39
@lihaojie-CMCC
Copy link
Contributor Author

This PR is ready for review.

Copy link
Contributor

@tanjadegroot tanjadegroot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Overall looks good !
a few fixes and comments, some of which can be delayed till next release (up to the team).

Side comment, generally in the API yamls some more description fields would be good.

@tanjadegroot
Copy link
Contributor

@lihaojie-CMCC, Team, any idea when you can do the updates (most are straightforward fixes) so we can go ahead and approve for merge and release.
We are targeting M4 and M5 (publication of the meta-release) in the TSC meeting tomorrow (4PM CEST).
thanks !

lihaojie-CMCC and others added 16 commits September 18, 2025 10:14
Co-authored-by: Tanja de Groot <87864067+tanjadegroot@users.noreply.github.com>
Co-authored-by: Tanja de Groot <87864067+tanjadegroot@users.noreply.github.com>
Co-authored-by: Tanja de Groot <87864067+tanjadegroot@users.noreply.github.com>
Co-authored-by: Tanja de Groot <87864067+tanjadegroot@users.noreply.github.com>
…hecklist.md

Co-authored-by: Tanja de Groot <87864067+tanjadegroot@users.noreply.github.com>
…ness-Checklist.md

Co-authored-by: Tanja de Groot <87864067+tanjadegroot@users.noreply.github.com>
…ness-Checklist.md

Co-authored-by: Tanja de Groot <87864067+tanjadegroot@users.noreply.github.com>
…ness-Checklist.md

Co-authored-by: Tanja de Groot <87864067+tanjadegroot@users.noreply.github.com>
@lihaojie-CMCC
Copy link
Contributor Author

@lihaojie-CMCC, Team, any idea when you can do the updates (most are straightforward fixes) so we can go ahead and approve for merge and release. We are targeting M4 and M5 (publication of the meta-release) in the TSC meeting tomorrow (4PM CEST). thanks !

Hi @tanjadegroot , Thank you so much for your comments. They are incredibly valuable to our project. We have implemented all the suggestions and completed the updates. Please take a look when you have a moment.
Also, sorry for the delayed response!

tanjadegroot
tanjadegroot previously approved these changes Sep 18, 2025
Copy link
Contributor

@tanjadegroot tanjadegroot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Many thanks @lihaojie-CMCC for the quick update !
A left a few comments still but you can decide if you do them before merging or if you leave them to the next release (as they do not impact the API usage)

All the rest looks great ! thanks

LGTM from Release Management

After the merge, please create the release and update the release trackers on the wiki - many thanks !

It is designed to provide applications with standardized capabilities for knowledge content storage and management, supporting multi-format document storage, fine-grained permission control, and end-to-end traceability.
It is suitable for building knowledge-intensive systems (such as intelligent customer service platforms and enterprise document platforms) while ensuring compliance.

It must follow RFC 3339 and must have time zone. Recommended format is yyyy-MM-dd'T'HH:mm:ss.SSSZ.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this text should actually be part of the schema definition you can copy it from https://github.com/camaraproject/Commonalities/blob/main/artifacts/CAMARA_common.yaml

Same for all yaml files using date-time type attributes

description: >-
This API provides CRUD (Create, Read, Update, Delete) management functions for the Question and Answer (Q&A) Assistant, aiming to equip developers with the capability to configure and manage intelligent question-answering systems based on Large Language Models (LLMs).
It supports model parameter tuning, knowledge base association, and prompt engineering configuration, making it suitable for building customizable intelligent customer service or question-answering services.
It must follow RFC 3339 and must have time zone. Recommended format is yyyy-MM-dd'T'HH:mm:ss.SSSZ.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same comment as above on date-time based schemas

description: >-
This API provides service interfaces for the Question and Answer (Q&A) Assistant, enabling users to submit query requests to a configured Q&A assistant and obtain answers generated based on the knowledge base and Large Language Model (LLM).
It is suitable for scenarios such as building intelligent question-answering systems and customer service bots that require real-time responses to user inquiries.
It must follow RFC 3339 and must have time zone. Recommended format is yyyy-MM-dd'T'HH:mm:ss.SSSZ.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same comment as above on date-time based schemas

Co-authored-by: Herbert Damker <herbert.damker@telekom.de>
@lihaojie-CMCC
Copy link
Contributor Author

Thanks everyone for the review and feedback! I'm going to go ahead and merge this PR.
The relevant revisions will be addressed in the next release.

@lihaojie-CMCC
Copy link
Contributor Author

@hdamker @tanjadegroot , As we've just revised the "consumer" related content, we would like to seek your assistance for a final confirmation from the Release Management side. We greatly appreciate your support!

Copy link
Contributor

@tanjadegroot tanjadegroot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

All good - thanks very much for the updates !!

LGTM from Release Management

@lihaojie-CMCC lihaojie-CMCC merged commit 2a21956 into main Sep 18, 2025
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants