Contribution Guidelines
Search…
Contribution Guide (en)
Overview
Preface
Workflow with JIRA Issues
Introduction
<OPEN>: Register a JIRA issue
<Confirmed>: Issue Triage
<In Progress>: Task in Progress
<Review In Progress, Reviewed>: Task Review
<Resolved>: Task Complete
<Closed>: Issue Termination
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
Overview
CUBRID is an open source project that operates on the basis of a general open source project development process. The developers of CUBRID contribute to one big project called CUBRID by using collaboration tools for open source development projects.
The purpose of this document is to describe the development workflow using collaborative tools and to establish the basic principles for mutual consensus on a development culture. This document can be flexibly applied according to the situation and modify/develop through mutual agreement:
  • Individuals and interactions over processes and tools
  • Working software over comprehensive documentation
  • Responding to change over following a plan
The CUBRID development process is based on the following two tools:
All CUBRID projects, feature additions, and bug fixes start with the creation of JIRA issues. In accordance with JIRA's Issue workflow, contributors will begin designing and implementing their problem after defining and investigating it. In the design and implementation stage, the code is merged in CUBRID after the review through branch creation, Pull Request, and code review on Github. CUBRID is developed sustainably by repeating the above process.
Next
Preface
Last modified 1yr ago
Export as PDF
Copy link