> For the complete documentation index, see [llms.txt](https://daton-sarasanalytics.gitbook.io/halo/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://daton-sarasanalytics.gitbook.io/halo/skill-publish-cycle.md).

# Skill - Publish cycle

1. Testing completed successfully
2. Inform sales/marketing team to keep skill detail (strapi) page ready
3. Same app installed for other project on Dev and data was populated for new installed projects (including views data)
4. Release plan shared with Platform and Sales team  (Platform team may need 2-4 days buffer to  implement relevant Backend changes so keep them posted at the earliest)
5. All tables, models and reports validated/reviewed by Product group. 
   1. Please ensure Primary keys used are as expected for all entities.
   2. Variable syntax and definition is right
6. Skill - onboarding and understanding pages documented
7. Ensure all tables, models and reports are in published state on Dev. Delete redundant(not published) objects to keep it clean.
8. App run completed successfully and data can be seen for all published reports (Existing and new)
9. Before image captured for test client account
10. Platform and Sales team’s approval to start publish cycle
11. On Dev--> Go to admin panel --> manage apps --> Select app to be published --> click on Ready for publish
12. On Prod --> Go to admin panel --> manage apps --> Select app to be published à
    1. Publish --> to move changes from dev master to Prod master
    2. Reset/reload --> For same test client account which was used in steps 8. Validate After image against before image. 
    3. Reset/reload --> to run reset integration workflow for other active clients (Add details about 4 options)
13. Monitor and validate Airflow entries + job runs for initial 2 days
14. Monitor alerts for new sourceid on channel Halo Production Airflow Alert
15. App readiness to be shared with Sales team

Pending --> Global reports publish