| 2006-08-04 17:36:11 |
Matt Zimmerman |
description |
After creating a new release in Soyuz, I went to /+administer 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. |
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. |
|
| 2006-08-05 16:57:04 |
Celso Providelo |
soyuz: statusexplanation |
|
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. |
|
