Since the package has been released, It would be good idea to track release versions from now on. To do this, some simple branching model is in place. master branch should always contain a stable tested version (stable doesn't necessarily mean bug-free), development should happen on a dev branch, which should be merged into master whenever a new release is ready.
Also, it is a good idea to tag the released versions so that it is possible to determine which exact commit has been released as, say, release v0.2. Tagging is a git feateru, see $ git help tag or $ man git-tag.
Since the package has been released, It would be good idea to track release versions from now on. To do this, some simple branching model is in place.
masterbranch should always contain a stable tested version (stable doesn't necessarily mean bug-free), development should happen on adevbranch, which should be merged intomasterwhenever a new release is ready.Also, it is a good idea to tag the released versions so that it is possible to determine which exact commit has been released as, say, release v0.2. Tagging is a git feateru, see
$ git help tagor$ man git-tag.