> For the complete documentation index, see [llms.txt](https://dev.cubrid.org/dev-process/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://dev.cubrid.org/dev-process/dp-en/gh-guide/git-branch-model.md).

# Git Branch Model

Git branch is a useful tool that allows multiple developers to work on multiple tasks at the same time on one piece of software for multiple purposes. For more detail, please refer to the [link](https://backlog.com/git-tutorial/kr/stepup/stepup1_1.html).

Most of the Github projects have serveral branches set for the purpose. For example, the *develop* branch keeps the latest developments, and the *master (or main)* branch manages the stable versions. There are several ways to run an open source project by leveraging each branch in a purposeful way.  CUBRID is operated based on the [Vincent Drissen branch model](https://nvie.com/posts/a-successful-git-branching-model/) which has been applied by many open source projects.

## CUBRID's Branch Model VS. VD Branch Model  <a href="#comparison-vd-cubrid" id="comparison-vd-cubrid"></a>

In the *Vincent Drissen model* (hereinafter referred to as the VD model), there are permanently maintained branches such as develop, master, and temporary branches such as release, feature, and hotfix. The difference between the CUBRID branch model and the VD model is that in the CUBRID branch model, we maintain the released version's branch permanently, (e.g. release/10.2, release/11.0). For example, even if the develop branch is on the latest version 12, the release/10.2 is also maintained for minor version upgrade releases 10.2.2, 10.2.3, 10.2.4...

In the VD model, a pre-release branch is created and it performs the same role as the release branch which is temporarily created during the release of the latest version. For more details, please see the [Release Section](/dev-process/dp-en/rel/release.md).

For issues that are difficult to complete with one Pull Request, you can utilize a feature branch. Feature branches are described in a separate section that follows.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://dev.cubrid.org/dev-process/dp-en/gh-guide/git-branch-model.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.