Version numbering

[danrubin]

Any thoughts on how we should determine a change from 0.1 onwards? I've not worked on a shared and versioned project like this with multiple authors, just curious what ya'll think is the best way to draw a version line in the virtual sand.

[nicemodernist]

Versioning could indeed be confusing as we move along as we're removing features as we move the source forward . Would it be wise to outline a small handful of milestones that could serve as version points? Or would that be equally confusing?

I'm new to multiple authors, too. Maybe I'm coming at it backward.

[cdharrison]

I like the idea of using milestones to determine what version the theme is at.

[splorp]

In terms of milestones, how about some of these (in no particular order):

• Initial decrufting finished (we’re fairly close to this point now, I believe)
• Code optimization
• Comprehensive code comments
• Adding a basic, typographic stylesheet
• Adding a basic, two-column layout stylesheet
• Adding custom shortcodes
• Adding custom widgets

Of course, all of us probably have specific ideas of where we see this theme going (and where the sister themes for other CMS need to go).

Perhaps we should start another issue thread where we can jot down our ideas (or requirements) for Tersus. Then we may be able to better pinpoint targets and milestones from that list.

[splorp]

I just gone ahead and started tagged versions to the project when “enough” changes have been made to the code base. I am documenting the general flavour of these changes in the version history section of the read me.

https://github.com/splorp/tersus#readme

Please let me know if you have any comments about this process.