Development Workflow

Branch Conventions

Ongoing development happens in a branch called next.

Only time-critical bugfixes go directly into master (but this will be the case only until Vundle is capable of locking to a version, after that, nothing gets commited to master).

When next has enough changes, it gets merged back to master. This is done after a PR has been created and discussed.

Versions

Vundle uses, currently, a relaxed form of semantic versioning. While Vundle has not reached version 1.0.0, this is how versions change:

When branch next is merged into master:

• PATCH is increased if the merge only includes bugfixes that don't change Vundle's externals.
• MINOR is increased if the merge includes at least one new feature or some change to Vundle's externals, even if it is of an optional nature.

Dealing with Issues

1. try to reproduce the issue.
2. close it if it's a non-issue
3. close if it's a duplicate referring for the original issue
4. decide whether it's a bug or feature or windows only issue
5. label it respectively
6. notify others for feedback or review if needed.
7. add yours...