Sat, Jul 13
Fri, Jul 12
Thu, Jul 4
I agree, it looks great!
Wed, Jul 3
Nice work. Go ahead and merge once you've confirmed it works.
Tue, Jul 2
network-manager-gnome, not network-manager-gnomer :)
Mon, Jul 1
Yeah, as far as I can tell, we had "ubuntu" as the machine-readable bootloader ID and "Lubuntu" as the human-readable.
This really depends on the functionality of Secureboot. If Secureboot is fine with the human-readable name saying "Lubuntu" and the machine-readable name saying "ubuntu", then we're fine here.
I think fullscreen is the best way to go here.
Everything under debian/lxqt-globalkeys-l10n needs to be removed.
Fairly nitpicky, but your modifications to the patch completely change the purpose. That's fine, but you can now just modify existing information Description, Author, and Bug instead of adding your own lines. Also, please modify Bug to say Bug-Ubuntu, which follows DEP-3.
Ah, indeed. I didn't even think that would be a problem, huh.
Sat, Jun 29
Tue, Jun 18
May 6 2019
Are you referring to rLUBUNTUMETAPACKAGING lubuntu-meta Packaging?
Let me talk to the SRU team and see what their thoughts are on SRUing such a patch.
May 4 2019
May 3 2019
Apr 25 2019
Apr 19 2019
Alright, I'm writing this all down in one place so I don't forget and others can rubber ducky me. Basically, we need to set Calamares up to configure some custom settings, iff the OEM GRUB entry is set. This isn't horribly complicated at all.
Apr 18 2019
Exactly. Move everything over, it doesn't belong here. :P
Put it in rNEWREL New Release Tooling :P
Apr 16 2019
I would suggest we just add this to rNEWREL New Release Tooling, sort of like how the Ubuntu release checklist is.
Check my kind of English and convert it into real English
I can count, I swear!
Apr 15 2019
@wxl could you please make a separate task?
You hit the nail on the head @wxl :)
I just talked with a member of the Ubuntu Technical Board; it is a platform expectation that we do not modify this, because the base is Ubuntu.
and would function the same as selecting the boot entry (on BIOS I think?)
You now have push access; while I need to manually deploy any changes you make to prod, feel free to push whatever changes directly to master.
I said on the devel channel yesterday(?) that I think it's too late for release, but seeing as it's default in Virtualbox, it makes it much more urgent in my eyes. If we want to retest everything, Adam did say this on Thursday...
[20:53] <infinity> tsimonq2: Ultimately, for packages only you seed, you have final say anyway (up to a point). If you want to upload something and respin and retest all your crap 6 hours before release, be my guest. [20:53] <infinity> tsimonq2: If you want to do it an hour before release, you might have missed your window. :P
That being said, I want @guiverc's input on this, because he's the AWESOME (seriously!) tester who has been plowing through the testcases.
Packageset updates are manual, and I poked cyphermox at one point. I'll poke him again, at which point we can close this task, I think.
The new "Next Generation" installer subiquity is supposed to replace ubiquity
Also, @teward has more experience with this, but once we get something working, we need a systemd unit (again, probably mirrored after Fedora's) and some packaging (which I can handle).