-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make new versions clearer in the submission system #2282
Comments
rafgia
added a commit
that referenced
this issue
Sep 26, 2024
…there are older versions of that project. A message is displayed when the project is a new version, and the reviewer can click on a link to view the latest published version. Closed #2282#.
rafgia
added a commit
that referenced
this issue
Oct 1, 2024
… published project, a message is displayed alongside the version number stating, 'This is an update of the latest published version. Otherwise, a message stating 'No latest version available' is displayed. #2282 closed.
This was referenced Oct 2, 2024
rafgia
added a commit
that referenced
this issue
Oct 2, 2024
… published project, a message is displayed alongside the version number stating, '(this is an update to a published project)'. Otherwise, a message stating 'Latest Published Version: No published version available.' is displayed. #2282 closed.
rafgia
added a commit
that referenced
this issue
Oct 3, 2024
… published project, a message is displayed alongside the version number stating, '(this is an update to a published project)'. Otherwise, a message stating 'Latest Published Version: No published version available.' is displayed. #2282 closed.
rafgia
added a commit
that referenced
this issue
Oct 3, 2024
… published project, a message is displayed alongside the version number stating, '(this is an update to a published project)'. Otherwise, a message stating 'Latest Published Version: No published version available.' is displayed. #2282 closed.
rafgia
added a commit
that referenced
this issue
Oct 3, 2024
… published project, a message is displayed alongside the version number stating, 'This is an update of the latest published version. Otherwise, a message stating 'No latest version available' is displayed. #2282 closed. On the Project Submission Info page, when there is a new version of a published project, a message is displayed alongside the version number stating, '(this is an update to a published project)'. Otherwise, a message stating 'Latest Published Version: No published version available.' is displayed. #2282 closed. On the Project Submission Info page, when there is a new version of a published project, a message is displayed alongside the version number stating, '(this is an update to a published project)'. Otherwise, a message stating 'Latest Published Version: No published version available.' is displayed. #2282 closed. On the Project Submission Info page, when there is a new version of a published project, a message is displayed alongside the version number stating, '(this is an update to a published project)'. Otherwise, a message stating 'Latest Published Version: No published version available.' is displayed. #2282 closed.
tompollard
added a commit
that referenced
this issue
Oct 3, 2024
On the Project Submission Info page, when there is a new version of a published project, a message is displayed alongside the version number stating, 'This is an update of the latest published version'. Otherwise, a message stating 'No latest version available' is displayed. #2282 closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When reviewing a project, it is not immediately obvious when the project is a new version of an existing published project. We should highlight new versions, because typically they only need a light review.
The text was updated successfully, but these errors were encountered: