Let’s fix the versioning scheme of Seamly. It’s not reflective of where the software is.
Semantic versioning (where each number and the placement of the number indicates meaning)is best, as @Douglas suggested:
That’s because way back in the day they decided that version 1.0 would have all the features needed for a lay user to draft & cut a pattern that fits. Since one of the core features is supposed to be Seamly3D, which will allow one to fix egregious fit issues before translating to the material world, we’re still a good way from v1.0, but I think we should be at least to ß0.6.2.0
More about Semantic versioning here:
The one-page guide to Semver: usage, examples, links, snippets, and more.
A Computer Science portal for geeks. It contains well written, well thought and well explained computer science and programming articles, quizzes and practice/competitive programming/company interview Questions.
Software versioning is the process of assigning either unique version names or unique version numbers to unique states of computer software. Within a given version number category (e.g., major or minor), these numbers are generally assigned in increasing order and correspond to new developments in the software. At a fine-grained level, revision control is used for keeping track of incrementally-different versions of information, whether or not this information is computer software, in order to ...
2 Likes