Details
-
Type: Task
-
Status: Closed (View Workflow)
-
Priority: Major
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: None
-
Labels:
-
Story Points:5
-
Epic Link:
-
Sprint:Fall 6 : 28 Oct to 8 Nov, Fall 7 : 11 Nov to 22 Nov
Description
Release Model:
App -> App (Symbolic Name)
Bundle_Version -> Current Release Version
Works_With -> Compatibility
Notes -> UI Field (Not Sure if we need this)
Created -> Date the Release was Created
Active -> Can be removed or kept depending on the Delete Functionality
Logo -> Release Related Logo
Bundle_Description -> Bundle(Release) Specific Description
Repository_XML -> Repository.xml from the Bundle
Release_File -> Release File Location usually /releases/symbolicname/version/symbolicname-version.jar
HexCheksum -> JAR Checksum to validate
Apps Model:
Bundle_Name -> Can be removed but in future scope
Bundle_SymbolicName -> Application Unique Symbolic Name
short_title -> Short Description about the app
Bundle_Description -> Long Description about the app
Bundle_Version -> Latest Version (Used by UI to retrive data from the Releases Model)
categories -> App can be connected to a category or Tag Cloud
authors -> Authors of the App
editors -> Users who can edit the App
has_releases ->
logo -> REMOVE (Can be retrived from the Releases Model)
release_file -> REMOVE (Can be retrived from the Releases Model)
release_file_name -> REMOVE (Can be retrived from the Releases Model)
license_url -> App Specific Licence
license_confirm -> UI Required Field
website_url -> App Specific website
tutorial_url -> App Specific tutorial
citation -> App Specific Citations
code_repository_url -> App Specific Code Repo
contact_email -> Developer Contact Email
stars -> App Specific Stars
downloads-> App Specific Downloads
repository_xml -> REMOVE (Can be retrived from the Releases Model)
active -> Can be removed if we make the Delete Functionality Redundand
Attachments
Issue Links
- relates to
-
IGBF-2131 To populate all fields of new version of released app from previous highest released app in Releases model
- Closed
-
IGBF-2132 Fixing Javascript related to Sorting and Categories after Appstore Refactoring
- Closed
-
IGBF-2106 App Page not getting updated once a release app is deleted
- Closed
-
IGBF-2084 Refactor App Store release and app models
- Closed
Activity
Field | Original Value | New Value |
---|---|---|
Epic Link | IGBF-1388 [ 17463 ] |
Description |
Release Model:
App -> App (Symbolic Name) Bundle_Version -> Current Release Version Works_With -> Compatibility *Notes -> UI Field (Not Sure if we need this)* Created -> Date the Release was Created Active -> Can be removed or kept depending on the Delete Functionality Logo -> Release Related Logo Bundle_Description -> Bundle(Release) Specific Description Repository_XML -> Repository.xml from the Bundle Release_File -> Release File Location usually /releases/symbolicname/version/symbolicname-version.jar HexCheksum -> JAR Checksum to validate Apps Model: Bundle_Name -> Can be removed but in future scope Bundle_SymbolicName -> Application Unique Symbolic Name short_title -> Short Description about the app Bundle_Description -> Long Description about the app Bundle_Version -> Latest Version (Used by UI to retrive data from the Releases Model) categories -> App can be connected to a category or Tag Cloud authors -> Authors of the App editors -> Users who can edit the App has_releases -> *logo -> REMOVE (Can be retrived from the Releases Model) release_file -> REMOVE (Can be retrived from the Releases Model) release_file_name -> REMOVE (Can be retrived from the Releases Model)* license_url -> App Specific Licence license_confirm -> UI Required Field website_url -> App Specific website tutorial_url -> App Specific tutorial citation -> App Specific Citations code_repository_url -> App Specific Code Repo contact_email -> Developer Contact Email stars -> App Specific Stars downloads-> App Specific Downloads *repository_xml -> REMOVE (Can be retrived from the Releases Model) active -> Can be removed if we make the Delete Functionality Redundand* |
Release Model:
App -> App (Symbolic Name) Bundle_Version -> Current Release Version Works_With -> Compatibility *Notes -> UI Field (Not Sure if we need this)* Created -> Date the Release was Created Active -> Can be removed or kept depending on the Delete Functionality Logo -> Release Related Logo Bundle_Description -> Bundle(Release) Specific Description Repository_XML -> Repository.xml from the Bundle Release_File -> Release File Location usually /releases/symbolicname/version/symbolicname-version.jar HexCheksum -> JAR Checksum to validate Apps Model: Bundle_Name -> Can be removed but in future scope Bundle_SymbolicName -> Application Unique Symbolic Name short_title -> Short Description about the app Bundle_Description -> Long Description about the app Bundle_Version -> Latest Version (Used by UI to retrive data from the Releases Model) categories -> App can be connected to a category or Tag Cloud authors -> Authors of the App editors -> Users who can edit the App has_releases -> *logo -> REMOVE (Can be retrived from the Releases Model)* *release_file -> REMOVE (Can be retrived from the Releases Model)* *release_file_name -> REMOVE (Can be retrived from the Releases Model)* license_url -> App Specific Licence license_confirm -> UI Required Field website_url -> App Specific website tutorial_url -> App Specific tutorial citation -> App Specific Citations code_repository_url -> App Specific Code Repo contact_email -> Developer Contact Email stars -> App Specific Stars downloads-> App Specific Downloads *repository_xml -> REMOVE (Can be retrived from the Releases Model)* *active -> Can be removed if we make the Delete Functionality Redundand* |
Status | To-Do [ 10305 ] | In Progress [ 3 ] |
Sprint | Fall 6 : 28 Oct to 8 Nov [ 77 ] | Fall 6 : 28 Oct to 8 Nov, Fall 7 : 11 Nov to 22 Nov [ 77, 78 ] |
Rank | Ranked higher |
Status | In Progress [ 3 ] | Needs 1st Level Review [ 10005 ] |
Assignee | Sameer Shanbhag [ sameer ] |
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 ] |
Assignee | Pawan Bole [ pbole ] |
Status | Merged Needs Testing [ 10002 ] | Post-merge Testing In Progress [ 10003 ] |
Resolution | Done [ 10000 ] | |
Status | Post-merge Testing In Progress [ 10003 ] | Closed [ 6 ] |
Assignee | Pawan Bole [ pbole ] | Sameer Shanbhag [ sameer ] |
Second draft of app and release models:
Release Model:
App -> App (Symbolic Name)
Bundle_Name -> provided by MANIFEST.MF Bundle-Name field
Bundle_Version -> provided by MANIFEST.MF Bundle-Version field
short_title -> Short Description about the app - provided by user
authors -> Authors of the App (from user originally, FK to Author table)
license_url -> App Specific Licence (manually entered by user)
license_confirm -> UI Required Field (manually entered by user)
website_url -> App Specific website (manually entered by user)
tutorial_url -> App Specific tutorial (manually entered by user)
citation -> App Specific Citations (manually entered by user)
code_repository_url -> App Specific Code Repo (manually entered by user)
contact_email -> Developer Contact Email (manually entered by user)
stars -> App Specific Stars (updated interactively on the UI by Web site visitors)
downloads-> App Specific Downloads (tracked by us)
Created -> Date the Release was Created
Active -> If false, the UI and OBR endpoint do not show this release
Logo -> Release Related Logo
Bundle_Description -> Bundle (Release) Specific Description (comes originally from MANIFEST.MF but can be edited by logged-in editor)
Repository_XML -> Repository.xml from the Bundle (comes originally from jar)
Release_File -> File object that stores location of jar file, Release File Location usually /releases/symbolicname/version/symbolicname-version.jar
HexCheksum -> JAR Checksum to validate
platform_compatibility - a string parsed from repository.xml (formerly "works_with"), not null
Note: platform_compatibility refers to IGB platform version
Later, we might also fill in the following fields:
lower_inclusive - boolean
lower_major - NOT null
lower_minor - NOT null
lower_micro - NOT null
upper_inclusive - boolean
upper_major - default is null
upper_minor - default is null
upper_micro - default is null
Note: Python knows how to compare version strings! e.g., "11.0.1" > "10.0" evaluates to true!
Apps Model:
Bundle_SymbolicName -> Application Unique Symbolic Name
categories -> App can be connected to a category or Tag Cloud
editors -> Users who can edit the App
Example:
If lower_major, lower_minor, lower_micro is 1.0.0 but "upper" fields are NULL – this App can work with any platform with version 1.0.0 and above.
This could come from compatibility string of 9.1.0