Conventions

Issue Creation

Each issue begins with the codes of the team or topic that is the issue related to and then the number of the issue.

General formula is <DEPARTMENT_NAME>-<ISSUE_NUMBER>: <ISSUE_NAME>

Codes:

• GEN for general issues.
• FE for frontend related issues.
• BE for backend related issues.
• MOB for mobile related issues.
• MILX for milestone issues. X denotes the number of milestone.

Examples:
GEN-21: Create a Wikipage for Conventions
BE-3: PostreSQL Integration to the application
GEN-7: Update the Communication Plan

Branch Naming

Let's say there is an issue named BE-13 (13th issue belonging to Backend team).
Then the related branch name should be in this format: feature/BE-13. First part indicates the purpose of the branch.
It can be test, bugfix, hotfix and feature.

Definitions <br>

feature simply stands for the implementation of anything new.
bugfix is used for fix of a bug (not too small).
hotfix is again used for bugs, but this time you just change 1-2 line of codes.
test stands for branches we opened for testing, they are not really important and probably won't be merged to master.