make releases and keep a changelog

[anarcat]

I love this project. Unfortunately, i don't have time to review every commit and pull request that is merged in, even on a monthly basis.

Instead, I would like if actual tags (ie. also tarball releases!) would be laid down, with a descriptions of broad changes that have been factored into those releases.

I would of course suggest semantic versionning for the versionning scheme, and would suggest you start with a 1.0.0 release. :)

Thanks!

[miketheman]

@anarcat That's an interesting idea - and not an impossible one.

I think part of this current project's goal was to reflect a living document, without actual releases just yet - it's possibly a little too young for that.

Unless there's a compelling reason to produce a deliverable? The content is available where needed.

[anarcat]

Well, the compelling reason for me is that I want to keep track of changes to the document in a more general view.

As for the "age" of the document, I don't think it's too young. There's already great information in there and it could only improve with further distribution that releases would bring. I can think of shipping this as a debian package for example...

This will always be a living document, hopefully, as our profession grows and changes all the time. Of course, some of the basics need to be covered, but the goals currently set in the document are so ambitious that I can't forsee when those will be accomplished enough that a warrant will be acceptable. :)

Release early, release often they say. https://en.wikipedia.org/wiki/Release_early%2C_release_often