Any update on this @lynorian? You don't really have a time limit here, but just know that master gets deployed on release day, so you might consider polishing from here. Up to you, just making you aware of what's going on.
Oct 3 2019
This really needs to be done by the end of this week so we can get the release properly tested.
What are the thoughts on this?
Making the executive decision that this is our new Lenny.
Bump, how was this going? Do we have everything set for release?
To clarify: let's not sponsor this to Ubuntu first, let's get this in Debian first (the right way).
@wxl Your next step is filing a Request For Salvage bug in Debian. Let me know if you need any help, and I'll be happy to sponsor it if the process is complete.
@apt-ghetto Leaving this to your discretion on whether or not you want to get the new nm-tray in before release. If you do, let's get that done before the weekend (I have to clear it with the release team but it should be no issue).
Bump, because I'd like to deploy this on release day if it's feasible.
Oct 1 2019
Alright folks, we're in the final stretch, we have about two and a half weeks. Let's work on a final push to get the Eoan Ermine out the door without problems!
That's a good idea. What about renaming the old branches to follow XX.YY? We could then follow the existing procedure, and you could go ahead and delete branches when you think it's necessary.
Sep 30 2019
Sep 27 2019
Sep 24 2019
You have to use the web GUI and manually add each one. Takes about 30-60 seconds each.
Sep 23 2019
This really needs to be done by the end of the day so we can get it in on time; I don't mean to be a pain but we need to move forward here.
I say we just push the commit directly to the Git repository and audit the commit once it's pushed. I trust Dan enough to know that he knows what he's doing.
This is a very very rough draft release announcement. Please look it over.
I have an inline question but it's not a FIXME so I'll go ahead and mark this as good.
Comments inline, otherwise LGTM.
@guiverc The number is assigned once the commit is merged; it is the same as the internal ISO QA tracker number referencing the testcase.
Sep 17 2019
Nice work testing, @guiverc. Here are the notable bugs:
- lxqt-panel: menu-button opens in wrong position (on portrait display, normal on landscape..)
- Can someone work with upstream to diagnose this? It seems fairly trivial.
- Ubuntu 19.04/19.10 qa:test - suspended system resumed without audio (fixed with pavucontrol toggle)
- We should definitely look at this before the final release, but there's a workaround, so I don't consider it RC.
- Lubuntu Daily ISO (May 19) QtPass error GnuPG not found
- This is a trivial fix, and it just involves fixing the default config. Could someone please look at cherry-picking the upstream fixes?
- /proc/self/maps paths missing on live session (was vlc won't start; eoan 19.10 & bionic 18.04 ubuntu/lubuntu/kubuntu/xubuntu/ubuntu-mate dailies)
- I consider this an RC bug. I will raise this with Adam and the kernel team before EOD today, because it needs to get looked at. It affects the end user experience when they're trying Lubuntu.
Sep 16 2019
Sep 13 2019
I have no preference here, do what y'all think is right.
Thanks for your work here! Looks good to me, it just needs some quick changelog fixes.
Sep 4 2019
Aug 29 2019
Aug 22 2019
Don't SRU. Let's close it.
+1 on that approach @wxl, let's do it.
Aug 21 2019
As long as the new file is installed, this is fine
Aug 20 2019
Aug 18 2019
How are you ensuring the menu's cache is being updated?
I don't know this one off the top of my head, but you should see what environment variable the menu reads from to determine whether or not to show menu items. Probably in lxqt-panel.
The current state of the VCS does not match what's currently in the archive, when there's a slightly different changelog entry and a tag that should exist in the VCS. Please don't do this all in one commit, make importing from the archive its own commit and tag it.
Aug 16 2019
Aug 14 2019
@wxl please import all changes from the archive into the VCS and tag prior to landing this.
Aug 13 2019
This isn't a question of who as much as it is a question of how. :)
Aug 12 2019
Aug 11 2019
Go ahead with merging, uploading, and tagging.
Makes sense, thanks Dan :)
When you bump the debhelper compat, you also have to bump the dependency in debian/control. Please also say that no changes were needed in the changelog (obviously if there were, you would describe them).
Aug 10 2019
What you're suggesting is correct, @apt-ghetto. This should really be addressed upstream, but for now, we have our hacky workaround. :)
It would be done via a postinst script.
I don't know that I'm completely comfortable with this approach.
Oh, and additionally, it's an unwritten best practice to say "no changes needed" with std-ver and debhelper compat bump if no changes were needed. This is for clarity.
Aug 8 2019
Should propagate to Mastodon shortly.
Aug 3 2019
Sounds good to me.
I say we either switch to the fork before 19.10 is released or after 20.04 is released. I'm uncomfortable making such a change in the 20.04 cycle.