From the other thread on this here:
I post about this on Ask Ubuntu here - https://askubuntu.com/a/1566298/10616 - where I give what details are currently available to the public.
Note that this has been going on for over 12 hours at this point. There hasn’t been an official response from Canonical yet.
My suggestion to the Community (with my Community Council hat on! ) is to not speculate further, or attack / target Canonical with your concerns, or similar. Let’s simply acknowledge this is going on, but then wait to see how it develops.
There’s not much we - the community - can do on this front other than “wait to see what happens”, so let’s be patient and let Canonical play catch-up and address the issue. Until then, we should just wait - not speculate on what’s going on, nor point fingers at Canonical or anyone else, nor chastise this as a Canonical problem, or whatever. That doesn’t serve a useful purpose at this time.
I’ll keep my Ask Ubuntu post up to date as public information is available, but as I said in my other post, let’s avoid speculation at the moment and let Canonical catch up enough to address the ongoing issues and then come out with official action / after-incident reports.
4 Likes