After creating a new release, /+admin has null required field (Changeslist)

Bug #55209 reported by Matt Zimmerman
4
Affects Status Importance Assigned to Milestone
Launchpad itself
Triaged
Low
Unassigned

Bug Description

After creating a new release in Soyuz, I went to /+admin to set its release status. After changing only that field, I submitted the form, but it failed validation because the Changeslist input was empty. Either it should be required when creating the release as well, or should not be required in either context.

I think that having no changes email address for a release is OK.

Matt Zimmerman (mdz)
description: updated
Revision history for this message
Celso Providelo (cprov) wrote :

Right, to simplify all wierdness related to UploadPolicy.announcelist and DistroRelease.changeslist would be definately acceptable to have "changeslist" as a required attribute when adding a new distrorelase.

Otherwise, we could let "changeslist" as an optional attribute and include subtasks in the planned "Upload Policy Redesign" major task, to fix IDistroRelease, modify UploadPolicy.announce_list and other bits in NascentUpload.

Personally, the former would be cheaper and faster, for now.

Changed in soyuz:
importance: Untriaged → Low
status: Unconfirmed → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.