-
Spike
-
Resolution: Done
-
Major
-
None
-
None
-
Product / Portfolio Work
-
5
-
False
-
-
False
-
-
-
-
SF Train-28, SF Train-29, SF Train-31
-
None
Value Statement
In the OCM.io community, we always need to post update to different social medias, eg, slack, linkedin, twitter, etc, at the same time, to improve our impact. The goal is with just one chat, or watch the community update automatically, a post will be written by AI and reviewed by us, and then post auto to multiple social media.
Definition of Done for Engineering Story Owner (Checklist)
- ...
Development Complete
- The code is complete.
- Functionality is working.
- Any required downstream Docker file changes are made.
Tests Automated
- [ ] Unit/function tests have been automated and incorporated into the
build. - [ ] 100% automated unit/function test coverage for new or changed APIs.
Secure Design
- [ ] Security has been assessed and incorporated into your threat model.
Multidisciplinary Teams Readiness
- [ ] Create an informative documentation issue using the [Customer
Portal_doc_issue template](
https://github.com/stolostron/backlog/issues/new?assignees=&labels=squad%3Adoc&template=doc_issue.md&title=),
and ensure doc acceptance criteria is met. Link the development issue to
the doc issue. - [ ] Provide input to the QE team, and ensure QE acceptance criteria
(established between story owner and QE focal) are met.
Support Readiness
- [ ] The must-gather script has been updated.
- is cloned by
-
ACM-23979 Leverage AI to be more productive in upstream
-
- In Progress
-