According to the Which Projects are Covered? → section of the Security advisory process and permissions policy page:
Project maintainers may opt into security advisory coverage when they meet the requirements:
- A maintainer with “write to VCS access” has applied to have the "vetted" role, and received it.
- The project is a full project, not sandbox projects.
- There are no known security issues, open issues tagged “security” for the project.
- New projects must wait 10 days before opting in.
In addition to the previous issue I mentioned, there is an issue with using this negate in a context. Having a context with a menu condition with a negate will cause an Out of Memory error on the webserver even if the context is disabled.
This is a very useful addition, thanks.
One thing I have noticed with the patch is that if selected and saved, the next time you look at the setting in the GUI it visually appears as unchecked.
I have updated the Issue summary with a response to the related issue as well as an alternative proposed resolution of including a description for this permission.
jhuebsch → created an issue.
Thanks @SomebodySysop and @justclint. The TWO pages that had to be re-saved is what kept me up. I kept re-saving the "field settings" form not realizing I had to also save the "Fields" page form until I came across this issue.
I agree with bramvandenbulcke, this is a regression and will cause data collection loss for those who upgrade.
The fix has been in dev for 5 months, can we get a new release?
jhuebsch → created an issue.