On Tue, Nov 22, 2016 at 10:42 AM, Michel Rijnders <[email protected] > wrote:
> That's too simplistic, you can also break lots of projects by publishing a > version of a package with a serious bug. And what if it's a security bug > that somehow exposes sensitive information? In such a case unpublishing > makes sense. > These kind of concerns can be mitigated by upgrade policies and security audits. I think they are orthogonal to publishing. It would be, however, very very nice to add more defenses as time goes by. The world is a nasty place and tragedy can strike at any moment, sometime it pays to be extra careful. -- There is NO FATE, we are the creators. blog: http://damoc.ro/ -- You received this message because you are subscribed to the Google Groups "Elm Discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
