Git Issues Guidelines

This is a guideline on how to make, process, and describe issues.

##Issue Format [branch_name"<prefix>-<name>-*"][version"<major>.<minor>.<revision>"]: description

[feature-hmvc][3.1.0.95]: This issue is an issue, did we do recursion?

##Label Color Guideline

• All labels that are directly RELATED to Kunena and/or have an ACCEPTED status related to the definition of the label. The label will define a specific color of the normal color spectrum (red, orange, yellow, green, blue, purple) excluding tones of black and white.
• All labels that are directly RELATED to Kunena and/or have an PENDING status related to the definition of the label. The label will define a specific color black excluding tones of the normal color spectrum (red, orange, yellow, green, blue, purple) and white.
• All labels that are directly NOT RELATED to Kunena and/or have an REJECTED status related to the definition of the label. The label will define a specific color white excluding tones of the normal color spectrum (red, orange, yellow, green, blue, purple) and black.

##Label Descriptions

• <major>.<minor> Version when the issue was originally created.
• bug - Bug in implementation, does not always return expected behavior.
• crash - Crash in implementation, program does not exit correctly.
• docs - Documentation for current implementation. information.
• enhance - Current implementation is already in place but can be enhanced to include improved or modified behavior
• feature - Feature is an accepted proposal for implementation.
• fixed? - Implementation is available, but is the issue fixed regarding the context of the issue.
• joomla - Joomla specific problem.
• proposed - Proposed feature implementation.
• pull - Pending pull request.
• rejected -
• third party -
• top -
• unconfirmed -