Details
-
Type: Improvement
-
Status: Closed (View Workflow)
-
Priority: Major
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: None
-
Labels:None
-
Story Points:0.5
-
Epic Link:
-
Sprint:Fall 7 : 11 Nov to 22 Nov
Description
Many variable names in the module "apps" include "latest" and control core business logic. However, none of the App Store business logic should be using date or time to determine which app releases are shown to the user. Instead, we are using version and semantic versioning.
We require App developers to use proper semantic versioning for their Apps. This means we can easily sort Apps in order of version, from highest to lowest. "latest" has no meaning here.
Use of "latest" is confusing and potentially misleading to developers. Instead, we should use "highest" not "latest" in variable names.
To avoid confusing developers, remove all instances of "latest" in variable names in templates, except where the true purpose is to show the most recently submitted. Replace with "highest" instead.
Attachments
Activity
Field | Original Value | New Value |
---|---|---|
Epic Link | IGBF-1388 [ 17463 ] |
Rank | Ranked higher |
Assignee | Ann Loraine [ aloraine ] |
Summary | Replace "latest" with "highest" in "apps" module's templates, javascript, and py files | Replace "latest" with "highest" in "apps" module's templates, javascript, css, and py files |
Description |
Many variable names in the module "apps" include "latest" and control core business logic. However, none of the App Store business logic should be using date or time to determine which app releases are shown to the user. Instead, we are using version and semantic versioning.
This is confusing to developers. We require App developers to use proper semantic versioning for their Apps. This means we can easily sort Apps in order of version, from highest to lowest. "latest" has no meaning here. To avoid confusing developers, remove all instances of "latest" in variable names in templates, except where the true purpose is to show the most recently submitted. Replace with "highest" instead. |
Many variable names in the module "apps" include "latest" and control core business logic. However, none of the App Store business logic should be using date or time to determine which app releases are shown to the user. Instead, we are using version and semantic versioning.
We require App developers to use proper semantic versioning for their Apps. This means we can easily sort Apps in order of version, from highest to lowest. "latest" has no meaning here. Use of "latest" is confusing and potentially misleading to developers. Instead, we should use "highest" not "latest" in variable names. To avoid confusing developers, remove all instances of "latest" in variable names in templates, except where the true purpose is to show the most recently submitted. Replace with "highest" instead. |
Rank | Ranked higher |
Assignee | Sameer Shanbhag [ sameer ] |
Status | To-Do [ 10305 ] | In Progress [ 3 ] |
Status | In Progress [ 3 ] | Needs 1st Level Review [ 10005 ] |
Status | Needs 1st Level Review [ 10005 ] | First Level Review in Progress [ 10301 ] |
Status | First Level Review in Progress [ 10301 ] | Needs 1st Level Review [ 10005 ] |
Status | Needs 1st Level Review [ 10005 ] | First Level Review in Progress [ 10301 ] |
Status | First Level Review in Progress [ 10301 ] | Ready for Pull Request [ 10304 ] |
Status | Ready for Pull Request [ 10304 ] | Pull Request Submitted [ 10101 ] |
Status | Pull Request Submitted [ 10101 ] | Reviewing Pull Request [ 10303 ] |
Status | Reviewing Pull Request [ 10303 ] | Merged Needs Testing [ 10002 ] |
Status | Merged Needs Testing [ 10002 ] | Post-merge Testing In Progress [ 10003 ] |
Resolution | Done [ 10000 ] | |
Status | Post-merge Testing In Progress [ 10003 ] | Closed [ 6 ] |
Not In Scope as the latest and highest mean the same thing in the codebase. The latest Field is populated based on the highest version.
We might need this in the future but not now.