JOSE reviewers checklist: repository version
atrisovic opened this issue · comments
Hi there,
I noticed that reviewers are asked to check if the repository with the content for JOSE is released as a particular versioning number:
Version: Does the release version given match the GitHub release (1.0-1)?
However, in practice, the submitting author may create another release during or after the review, making this statement untrue and confusing for the reviewer. Also, the software does not recognize if there was no prior tagged release of the repository.
A good alternative that could solve these problems could be:
Version: Is there a recent tagged release on GitHub that captures the presented educational content?
I hope this makes sense, but I'm also happy to follow up.
Thank you,
Ana
hi @atrisovic – sincere apologies, but it turns out I wasn't "watching" this repository and have not come poking here in a long time (I had it set to "only when @-mentioned"... I changed it now).
Your comment makes sense: this item of the checklist has often confused reviewers. We do ask for a tagged release at the end of the review process, which then is updated with the command @whedon set v.x.x. as version. We will look into this.