...
- Always create a JIRA issue.
- Use meaningful comments when doing a commit/push/pull request.
- Always mention the JIRA issue that is related to your commit (e.g., "Fix for JIRA-123").
Especially use the JIRA issue ID(s) in the title of the pull request - in this case there is automatically created a link to your pull request in the according JIRA issue(s). - When doing a commit based on a patch from a contributor, make sure to mention the contributor name in the comment (e.g. "Fix for JIRA-123. (Contributor name)" ).
- Never commit incomplete changes (GIT is not a backup system).
- Working on experimental changes is encouraged, but in this case use a branch.
- Don't maintain Versions.txt anymore, we will extract release notes from JIRA starting from IzPack 4.0 and beyond.
- Subscibe to the developer mailing list to follow IzPack development conversations.
- Do not hesitate to pick new JIRA issues: both the other developers and the issue submitter will thank you for the work!
- When you start working on an issue, don't forget to mark it as in progress so that we know that you're solving it!
- For developing workflow will be: Open -> In progress -> Resolution -> Resolved -> Closed
- For language file update: Open -> Resolved -> Closed
- For more information about an issue please visit: What is an Issue?
...