Completely understand you @ian-weisser.
Most of the things I am referring to are not exactly bugs, so I will not consider them bugs to be discussed (except for the sound card). I have great respect for everybody involved and spending their energy on building a better ubuntu.
What I am trying to do is to summarize feedback from a user experience point of view. Of course I could enter a bug that I am missing my “workspaces” but then it will be closed with - “not a bug, this is by design” Because it is actually by design. Also I could open a bug with - “I upgraded and I no longer can boot my machine” and in this bug we would discuss all the different things about legacy boots and efi files, but the bug will be closed with “not a bug, this is a design decisions”. Because it is. But there are not many resource on which efi file exactly to choose when you finally manage to switch from legacy boot and have to choose one of the 8 files in the /ubuntu and /boot folders that are shown from the bios.
And we could go on here. Is it a bug that up until now for the last many versions I was able to use Alt+Tab and switch between windows in the current workspace but now suddenly I am switching between all the windows in all the workspace.
I think that these (along with all the other issues I had for the last 5 days. ) are not bugs from a developer and OS point of view.
What I would like to point out is that non of my colleagues including me had a seamless and issue free upgrade to ubuntu 18.04. Non of them have opened any bugs because as developers we understand that these are not bugs. This is more like how things were “decided” to be.
And non of us feels competent enough to take decisions about a future of an OS that we love and we’ve heavily invested in so we are thankful for the efforts that others have put into the process. But we could at least share feedback. Not detailed, log full, screenshot full, which versions of what you are using full feedback. But simple, user, “I don’t know why is this happening to me”, loosely defined, “without a single action to be taken”, feedback that I hope could help in future decision making process.
How do I think this might help - well for sure the upgrade process stopped a few times to tell me some things have changed in my configuration files- for apache and postgresql and asked me to diff them and accept on of the versions, but it did not for a moment stopped to tell be “look now, you will not be able to boot and we think it is important for you to know this”. Probably we could think of a way to properly inform the user. Or “look, we’ve decided to change to gnome because of reasons you could see here. Not everything would be like it is, but I see that you’ve used”. Should a user be bothered with such things during upgrade? I don’t know. Probably people have though about it and decided that users should not be bothered. Or probably they do not have data on whether people want to be bothered by this or not.
These are the ways I think such feedback could serve a purpose.