-
-
Notifications
You must be signed in to change notification settings - Fork 58
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Require release information #20
Comments
To clarify, we should ensure the submitted tag has a matching AppStream release version with something in the description, and fail if there's no matching release. We still need to human-review that release description if it does exist, but could avoid a lot of busy work/back and forth with developers if we fail early if it doesn't even exist. |
It looks like Flatpak will fail to build now without release info, so I think this can be considered as closed |
@danrabbit maybe I could have worded this better; does it fail if the release being submitted doesn't have info? Like it might have historical releases but we should automatically require info for the version we're building. |
Oh that's an interesting point. I'd imagine it can't differentiate. So it's probably worth reopening this |
I thought this existed, but I've come across a couple of updates in the reviewer dashboard that lacked AppStream release information for the release being published. We should fail and file an issue that release notes are always required for the latest release
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
The text was updated successfully, but these errors were encountered: