Implement a version scheme / releases

[Julian]

Implement a version scheme / releases

[nickl-]

I find the git flow model useful especially working in larger teams where more contributors have commit privs.

In short it suggests the use of the master branch as production ready with tagged release snapshots.
A develop branch with current development progress which gets merged back into master for release.
Feature branches for more complex feature enhancements which branches from develop and gets rebased on occasion to stay in sync and eliminate conflicts until it is completed and merged back into develop.

As for versioning scheme, I tend to auto-default to, the semantic versioning scheme which needs no introduction and is widely adopted and understood. Does any reservations against its use exist perhaps?

[Julian]

Nope, that's all reasonable sounding to me, it's how I generally do it too :). Sounds good to me.

[Julian]

Think we should tag a release to start?

[nickl-]

Did you tag?

Excuse the late reply I somehow thought that I did answer this but it was a looong and winding tale on how I usually only release when ready and then tag when releasing. Anyway you're blessed to have missed it.

=)

[Julian]

Heh :).

Should be tagged, yeah. https://github.com/json-schema/JSON-Schema-Test-Suite/tags