Adopt a versioning scheme and release cycle.

Ok I see your point, and I think the downsides outweigh my personal motivation issue :P

RELEASE(or whatever we could call it).MAJOR.MINOR.PATCH actually according to my proposal.

I think we should just try it with Githubs milestone feature instead of a roadmap.

Seems simple enough; to be fair we haven't really used it all that much before, but seeing as it's already there anyway... ;)

Oh, just one thing I forgot in the proposal, but I think we all agree about: A changelog should be included into the repository.

Yep, that's why I did another proposal just now, so we can init the branching model and release a 0.0.1.0 the first time we got something stable in the develop branch.

SemVer scheme +1 of course.
Timing: What about a time raster. IF there is a new release, release it at beginning of the month. (quarterly is to much I guess).
You have the idea of the two advantages - dependecies + admins ? I could elaborate.

just btw for the ruby gems releases this would be very useful (as guideline!)

Hm, pushing non hotfix releases on something like every second sunday could be an option to thing about. I've to think about it a bit more.

Yay! We have a versioning scheme :)

And https://github.com/diaspora/diaspora/pull/3589 gonna already shout it out via a custom header :P