Yep

This task remains here so that it does get added there.

Spite closes things, dummy.

The sloppy way we dealt with release notes and the website indicates how important things like this are.

It better be done. Cuz it's out.

It looks like the open stuff never got fixed, but oh well.

@hmollercl you're probably right, but I've seen cases where live works but the install doesn't. In any case, I want to know what Ubuntu proper does so we can emulate that. You have any interest in digging into that quagmire?

Looks like the golang stuff is gone. The others would be nice to remove, but we took care of the big stuff.

T63: Add support for Differential Revisions in Lugito

Just to make it easily accessible here's the line in the branding.desc that deals with window behavior.

Differential revisions, too.

And VirtualBox 6 I might add. That might also have something to do with it.

Well here's a weird thing: I haven't had any problem with 19.04 in VirtualBox booting to a reasonable size, i.e. not a little 800x600 screen. Whether or not that's true, I don't think we need to make it so urgent, especially when the release notes link to a bug that provides a simple workaround: go full screen.

Well, regardless of whether or not it's going to be subiquity (the "s" supposedly stands for server), there is supposedly a new installer in the works.

Hooooooooooooooooooooooooooooooooold up. Doesn't "check disc for defects" ultimately accomplish the same purpose, except that the user is not forced to run it? Couldn't we build that into the GRUB entry for loading the image, i.e. it would first check for defects and then boot the image?

Just created a bug regarding an 800x600 screen (default in VirtualBox). Fullscreen would fix this regardless of the solution upstream comes up with. I will note they don't like scroll bars so the code currently enlarges the window and adds a scroll bar only if necessary. Ew.

…but the golang stuff is still in our packageset. @tsimonq2 ?

I can confirm ubuntu-report is not in the platform seeds, at least in that I ran grep -R ubuntu-report * in the repo with no results.

@tsimonq2 I see that you accepted {D7} for disco. As of 20190413.1, ubuntu-report is still in there. Did we get it in too late for the ISO to build with it? (Also a side question: are seeds germinated as part of the ISO creation process or does that have its own cron job?).

I tried setting the global $BROWSER to to a null value and then changing the default and the file associations didn't get updated. Long story short just using the variable at all is problematic. I can't see of a good way to fix it until upstream switches mechanisms. ☹

OpenVPN is the go to standard for VPN. It's known to be secure and reliable. It's a requirement. L2TP is actually an unencrypted protocol, so IPsec is required to make it secure. There is some question as to whether or not IPsec has been compromised. Either way, the need for two protocols is slow. PPTP is common (Windows 95!) but known to be insecure (WINDOWS 95!). Now should we not use insecure protocols? We do have telnet and ftp still, so that's an argument for keeping these things. My concern is that given limited resources, we should focus on high priority items first and worry about low priority stuff later.

Ideally, SRUs would be for things without workarounds and this has one, technically, so I think not. That said, the browser is a crucial component thus there's a possibility of high impact, so maybe. We still need to explore a good fix. It seems we may have one coming from upstream soon.

All subtasks done. Good job everyone! Happy release day!

Sounds like it all makes sense after talking more to @hmollercl so closing.