WIP/RFC: revisit versioning #28
Conversation
| * It can be a drop-in replacement for setuptools_scm_ | ||
|
|
||
| # XXX: also "dev" and "devcommit"?! | ||
| # XXX: the code also handles "changes" (https://github.com/zsimic/setupmeta/blob/586102493f7167d47d633ff46eb9945ae36b730c/setupmeta/versioning.py#L305) |
There was a problem hiding this comment.
devcommit is described at bottom of page (very similar to dev, so I didn't put a section for it, maybe we should :) )
changes was the old name for distance, wasn't sure anyone ever used it, so left it there just in case.
| # XXX: also "dev" and "devcommit"?! | ||
| # XXX: the code also handles "changes" (https://github.com/zsimic/setupmeta/blob/586102493f7167d47d633ff46eb9945ae36b730c/setupmeta/versioning.py#L305) | ||
| # XXX: ...and "default", and "tag" | ||
| # XXX: s/strategies/formats/ ? (otherwise vice-versa below in the heading) |
There was a problem hiding this comment.
Ah yes, looks like I missed default and tag (which are the same as post)... should maybe remove those 2?
Regarding strategies, I picked that name because it was less common than format, and thought it conveyed the fact that there's a choice about how the version will evolve (e.g. you get different outcomes with post vs dev).
|
Thank you! Looks like I forgot to update that indeed, and there quite a few weird phrasings I didn't even realize were there :) |
2 participants
This fixes some wording, but more important adjusts the examples to what actually happens.
Not sure about if e.g.
.dirtywithversioning=postshould be used really instead of+g1, but I've actually tried it.. ;)I've left some "XXX" remarks - please comment / reply inline on the diff.