Contribution Guidelines
en-cg
en-cgko-cg
en-cg
en-cgko-cg
  • Overview
  • Preface
    • How to Read This Document
  • Workflow with JIRA Issues
    • Introduction
    • Open: Register a JIRA issue
    • Confirmed: Issue Triage
    • Analysis, Develop: Progress of Work
    • Handover: Cleaning Up the Task
    • Resolved: Completing the Task
    • Test: Testing
    • Backport: Backporting
    • Closed: Terminating Issues
  • Workflow with Github
    • Introduction
    • Git Workflow
    • Git Branch Model
    • Feature Branch
    • Pull Request, Code Review, Code Merge
    • Backport
  • Workflow after Code Merging
    • Checking the QA Report
    • Procedure Guide in case of Test Failure (Regression)
    • Manual Creation Guide
  • Contributing Guideline for First Contributors
    • Contributor License Agreement (CLA)
    • Good first issue
    • Communication Channel
  • Release
    • Release
Powered by GitBook
On this page

Was this helpful?

Export as PDF
  1. Workflow after Code Merging

Manual Creation Guide

PreviousProcedure Guide in case of Test Failure (Regression)NextContributor License Agreement (CLA)

Last updated 11 months ago

Was this helpful?

If the CUBRID manual needs to be updated during development or after development is completed, you can contribute in the same manner for and as in the guidelines described in previous sections.

  • Manual JIRA: ​

  • Manual Github: ​

Specifically, the manual creation process follows the below procedures:

  • Create a manual JIRA issue

  • Link the created manual JIRA with issues in CBRD or APIS projects

  • Create a Pull Request after creating a manual

  • Review PR for manual changes and code merge (includes previous versions)

  • Change the status of the manual JIRA to 'Done'

Manual JIRA
Manual Github
http://jira.cubrid.org/projects/CUBRIDMAN
https://github.com/CUBRID/cubrid-manual