RFE: Disable Severity for newpackage and enhancement updates

[mattdm]

Because, as Randy says:

"This newpackage update is urgently severe! Have some severe new features!"

If one of these update types is selected in the UI, the severity field should be changed to unspecified and the selector grayed out. And of course if an update is submitted via the api or whatever other means, that should either be rejected or the severity forced to unspecified.

[mattdm]

As a second enhancement linked to this, if an update is security or bugfix, then severity should be required. (And I suggest "medium" as the default.)

[kkofler]

A newpackage update can be urgent, if it is a new dependency of an upcoming urgent security update (think Firefox/Chromium-style packages that upgrade to new feature releases for security updates).

[kkofler]

Likewise, an enhancement update can be urgent if it is a bumped dependency of an upcoming urgent security update.

[bowlofeggs]

On 03/08/2018 03:07 PM, Kevin Kofler wrote: A newpackage update can be urgent, if it is a new dependency of an upcoming urgent security update (think Firefox/Chromium-style packages that upgrade to new feature releases for security updates).

Yeah that's a good point. Such a build could also be put into the same update as the security update when this happens, however.