-
Type: User story
-
Status: Resolved
-
Priority: Minor
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: Update Center
-
Tags:
-
Sprint:Sprint DesignTeam (5.9.4-1)
How update center should look like, taking into consideration all the past and coming evolutions: private marketplace, app definition, that makes the current version unusable.
Needs:
Update center side
- 3 steps: DL Nuxeo Platform -> Connect tab with login/pwd -> Registration form with your client id, application and configuration.
- Allow the dev mode
- Package tabs
A Registration form is:
- client name = Nuxeo
- app name = Intranet
- configuration = Production
- Version = 12.1
- Actions = Disconnect. Once disconnected, the user should fill the registration form again (step2) (or log in again ? - step1)
Once activated, the Dev Mode allows you to update your application (which package ? only Studio's packages ? one by one?).
Connect side
- My apps menu with list of all the apps + possibility to create a new app
- Configuration menu with list of all the config + possibility to create a new configuration, + edit and save or publish ( = release, version) + action to pull values from another configuration + view version history / revert
An app is:
- a name = My app
- an set of possible actions (share with other contacts, …)
A configuration is:
- editable and can pull data from another configuration
- name = my prod version
- description/ version comment = the v2 rely on ...
- target platform = 5.9.3
- Hotfix version = ..
- Public packages = DAM 5.9.3, DM 5.9.3, nuxeo-template-rendering-1.1, …
- Studio packages = myproject 1.1, myotherproject 1.0, … (depends on the target platform, filtered)
- Private packages = myPackage 1.1
- -> Save or Publish (is versionable)
- Feedback messages to alert user there are new versions of packages, targets, … available
- Feedback messages to see if a configuration or an app is currently used ?
- depends on
-
NXP-14275 Update Center > Mock up new screens
- Resolved