Sunil Mohan Adapa 73e55f06b4

upgrades: security: Don't with the technical term 'backports' in UI ...

- Call backports as 'Frequent Feature Updates'. This is make it easy for a
non-technical user to understand better what they are.

- Clearly recommend enabling backports as this is our current consensus.

- Explain that if backports are disabled, feature updates will come every 2
years or so.

- Show the status of backports on upgrades app even after it is enabled.
Disappearing options in the UI are generally confusing for users (hiding of
expand partition feature should be seen as exception rather than as example).

- Tone down the alarm on backports:

  - Rename 'Security Notice' to 'Frequent Feature Updates' in security page.

  - Remove 'on a best-effort basis' phrase, as everything in Debian is similar.

  - Set the activate button to primary priority rather than warning to make the
  user comfortable with it.

- Share translation strings across the two apps so that effort for translators
is reduced.

Signed-off-by: Sunil Mohan Adapa <sunil@medhas.org>
Reviewed-by: James Valleroy <jvalleroy@mailbox.org>

2020-07-19 07:10:44 -04:00

..

data

setup: Move app data files into respective apps

2019-03-17 16:20:57 -04:00

templates

upgrades: security: Don't with the technical term 'backports' in UI

2020-07-19 07:10:44 -04:00

tests

tests: functional: Re-organize step definitions and helper methods

2020-05-22 22:52:40 +05:30

__init__.py

*.py: Use SPDX license identifier

2020-02-19 14:38:55 +02:00

forms.py

*.py: Use SPDX license identifier

2020-02-19 14:38:55 +02:00

manifest.py

*.py: Use SPDX license identifier

2020-02-19 14:38:55 +02:00

urls.py

*.py: Use SPDX license identifier

2020-02-19 14:38:55 +02:00

views.py

upgrades: Use only sources file to determine if backports enabled

2020-07-13 14:44:13 -07:00