Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

JIRA

People

Estimate

Notes

Jira
serverGPII Issue Tracker
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId99d82d4e-fa5f-3aa1-9ed7-3b9c198d81db
keyGPII-4273

Joseph

Status
colourBlue
titlePULL REQUEST

  • gpii-universal: provide a means for the LFM to get the version of the solutions registry known to the CBFM
  • Five sub-tasks; see following rows.

Jira
serverGPII Issue Tracker
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId99d82d4e-fa5f-3aa1-9ed7-3b9c198d81db
keyGPII-4306

(GPII-4273 i)

Joseph

Status
colourGreen
titleDONE

GPII-4273 ii - Add '/revision' endpoint to the CBFMJoseph

Status
colourBlueGreen
titlepull requestDONE

  • Second sub-task of GPII-4273; CBFM supports a /revision endpoint.
  • Maintenance mode: merging changes from master to keep the code from going stale.
  • Reviews from Cindy and Antranig; changes made; waiting another reviewPull request merged.
  • https://github.com/GPII/universal/pull/837
GPII-4273 iii/iv/v - LFM requests the revision of universal from the CBFMJoseph

Status
colourBlue
titlePULL REQUEST

  • Modify LFM to get the gpii revision from the cloud (iii), calculate the url to GitHub, download the solutions registry file therefrom (iv), handle errors (v).
  • Solutions registry files from github could be "faked" – under investigation.
  • Also in maintenance mode with respect to tracking master: decision at last week's grooming meeting that loading remote solutions registry is not a priority right now.
  • https://github.com/GPII/universal/pull/840

Jira
serverGPII Issue Tracker
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId99d82d4e-fa5f-3aa1-9ed7-3b9c198d81db
keyGPII-4400

Joseph

Status
colourBlue
titlePULL REQUEST

  • Removal of 'web' based solutions and preferences sets that reference them.
  • Fixed BrowserChannel tests failures, using different (real) solutions.
  • Tony reviewed: suggests using mock solutions (and, hence, mock preferences, and mock device context).  Works for the tests at hand, but cause failures in the solutions/preferences verifications tests.
  • Noted the issues on the pull request.
  • https://github.com/GPII/universal/pull/858

Jira
serverGPII Issue Tracker
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId99d82d4e-fa5f-3aa1-9ed7-3b9c198d81db
keyGPII-3754

Joseph

Status
titleON HOLD

Process Reporter (linux):

Jira
serverGPII Issue Tracker
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId99d82d4e-fa5f-3aa1-9ed7-3b9c198d81db
keyGPII-442

JosephWaiting on review/merge
Status
titleON HOLD

Process Reporter (windows):

Jira
serverGPII Issue Tracker
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId99d82d4e-fa5f-3aa1-9ed7-3b9c198d81db
keyGPII-2493

Joseph

Status
titleON HOLD

Device Reporter/PlatformReporter (universal):

Jira
serverGPII Issue Tracker
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId99d82d4e-fa5f-3aa1-9ed7-3b9c198d81db
keyGPII-3120

  • Originally part of DeviceReporter work for reporting all screen resolutions
  • That work may no longer be necessary
  • But, the way the PlatformReporter is currently implemented can be improved by using context awarness
Joseph

Status
titleON HOLD

...