pyDive

pyDive copied to clipboard

Hi,

• pls add a dev branch so new developments do not break existing, working versions.
• please upload the 1.0 release tag you did locally via git push mainline --tags and name in properly
• please add a milestone for your new release and assign issues to it
• please write a change log for each pull request from dev -> master. these pull requests should directly define a release (and require a tag afterwards) as we all recommend [a successful git branching model](http://nvie.com/posts/a-successful-git-branching-model/

furthermore:

• pls think about using pull requests instead of direct push's to dev

fantastic you uploaded the tags!

pls don't forget about adding a small description to each tag online (what's new?) and writing change logs even for minor versions and revisions - so users know what's new, what was buggy and what interfaces changed/were/are broken.

Milestones, change log and tag annotations are still missing. Let us leave this open so the next release to master can write it.

great updates in the maintainer wiki, thank you! :sparkles: