Re: Lubuntu LTS Requalification: 24.04 Noble Numbat
Hello, I do appreciate the responses from my Lubuntu colleagues on this topic. That being said, Steve addressed me, so I at least owe him an acknowledgement. I will also address some common questions we have received recently. Firstly, Thomas is correct, and I agree that the Lubuntu Constitution[1] (as ratified by the Ubuntu Community Council) clearly defines these roles and positions. With Lubuntu being a large player in the Ubuntu ecosystem, a one-time read-through of our governing document may be beneficial. The reason Thomas Ward is Team Lead and I am Release Manager is simple: we both get to work on what we actually enjoy. I enjoy being Release Manager, and the responsibilities that come with it. Thomas enjoys being Team Lead because he is well-connected with the legal, financial, and infrastructure needs of the project, and that is what he enjoys doing. What I believe Thomas is trying to say is, he leaves the vast majority of day-to-day decisions to us, and is happy to delegate. After all, the Team Lead is just the head of the executive; he *is* required constitutionally speaking to run his decisions by the Lubuntu Council, and as a body, we do have the right to override him (which has not happened in recent memory, but the point still stands.) This all being said, there is no contention between Thomas and I; we're both actually quite happy with this arrangement, and have great mutual trust. Thomas is skilled at being the head of the executive, that being said, I would remind him that, while I agree that this is a high-stakes discussion that should be dealt with by official leadership, Aaron did the right thing by responding in this case. His response was helpful, and actually gave Steve the information he needed to make his decision. Don't Punish Good Behavior™ :) More responses in-line. On 1/17/24 11:18 PM, Thomas Ward wrote: > I was just about to reply with a decision from Team Lead and Council as > follows, which sort of affirms what Aaron said (though this DID need to come > from leadership, not Aaron): > > Primary contact: Simon (tsimonq2) > Secondary Contact: Dan (kc2bez) > Third-tier contact (if Simon and Dan don't reply): Aaron (arraybolt3) We'll be discussing this internally on a Lubuntu Council level after our next election cycle. I get the feeling that Dan and Aaron both need to be secondary contacts, but I'm okay with this being the decision for the time being. To be clear, this is only for Noble, and would not apply for e.g. point releases, which I have already explicitly delegated to both of them. > For an all else fails contact, you can contact me - Thomas (teward) - as > Lubuntu Team Lead, I have executive authority to act if others are > unreachable or in cases where it requires executive overrule (see Simon's > reference to me dictating the "rest period" for Lubuntu started on Dec 20 > instead of Simon's suggestion of Dec 25th through New Year). I don't think that exactly was public, but I'm okay with it being public now. :) > I'm also always open to pass on escalations if the others are unreachable, > Simon and Aaron both know I'm no stranger to dropping bags of work on them > when it's necessary. > > (Note that my Lubuntu duties are independent of my other roles and hats) (Thomas is actually pretty good about separating CC/etc. duties and Lubuntu duties, allow me to give him credit here.) > Thomas > > (Sorry for not replying in line, Outlook is the only mail client I have right > now and it's a pain for replying because it does top-replies). > > -Original Message----- > From: Ubuntu-release On Behalf Of > Steve Langasek > Sent: Thursday, January 18, 2024 12:14 AM > To: Aaron Rainbolt > Cc: Simon Quigley ; ubuntu-release@lists.ubuntu.com > Subject: Re: Lubuntu LTS Requalification: 24.04 Noble Numbat > > On Wed, Jan 17, 2024 at 10:34:04PM -0600, Aaron Rainbolt wrote: >>> One of the points on https://wiki.ubuntu.com/RecognizedFlavors for >>> LTS approval is > >>> Flavor's support plan presented to Tech Board and approved; support plan >>> should indicate period of time if beyond 9 months (3 yrs or 5 yr), key >>> contacts, and setting expectations as to level of support. > >>> Who are you identifying as the "contacts" for escalation of any >>> issues regarding Lubuntu 24.04 LTS, from the technical board or the release >>> team? > >> Perhaps this got missed, but in the Lubuntu Constitution (our personal >> "how things work in our project" policy), this is very well-defined. > > Well yes, that was not part of the information submitted to the Technical > Board as part of the qualification request. It's healt
Updating Lubuntu's Release Management Delegation
Dear Ubuntu Technical Board, Ubuntu Release Team, and Lubuntu Community, Proper delegation in any leadership position is critical for preventing bus factor, burnout, and de-motivation. At Lubuntu, we strive to set an example, and maintain contributors that significantly contribute to the project. As the officially-appointed Release Manager for the Lubuntu project, the Lubuntu Constitution[1] affords me the right and responsibility of selecting official Assistants to my position. These individuals assist with the duties of the Lubuntu Release Manager, which is defined as such in our Constitution: "The Lubuntu Release Manager is the individual responsible for all release management for the Product. They make the final decision as to what packages are in the Product (although this is subject to platform expectations set by the Ubuntu Technical Board), the release goals for the Product, and whether or not the Product is in a releasable state. They serve as the point of contact for Product releases, and have the ability to establish release-related rules for Product-specific packages." Therefore, the delegation for the Lubuntu Assistant Release Management Team has been updated to the following, effective immediately: - Aaron Rainbolt (arraybolt3) - Dan Simmons (kc2bez) As the current Lubuntu Release Manager, I hereby delegate Release Management of Long-Term Support Point Releases to the Lubuntu Assistant Release Management Team, beginning with the 22.04.4 point release. Our project governance explicitly dictates that this responsibility ultimately falls onto me, so if a decision needs to be made that is above the capacity of the aforementioned members, I will be available to make the "final call." That being said, my intent is to let them do these releases independently, which will allow me to focus on Release Management for the latest, upcoming stable release (in this case, 24.04). Per the decision of the Lubuntu Council, Thomas Ward remains as Team Lead. The Team Lead may be consulted in the case that every member of the official Release Management team is unavailable to carry out their duties, but treat this as an emergency, last-resort decision that surpasses the Release Management Team's rank. If you have any questions, please reach out to me personally. That being said, I would ask that the TB and Release Team accept this with open arms, and assist us in guiding Aaron and Dan in their Release Management duties. [1] https://git.lubuntu.me/lubuntu-wiki/wiki/wiki/Constitution Best regards, -- Simon Quigley si...@tsimonq2.net tsimonq2 on LiberaChat and OFTC @tsimonq2:ubuntu.com on Matrix 5C7A BEA2 0F86 3045 9CC8 C8B5 E27F 2CF8 458C 2FA4 smime.p7m Description: smime.p7m -- Ubuntu-release mailing list Ubuntu-release@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-release
Lubuntu LTS Requalification: 24.04 Noble Numbat
te is because I instructed all Lubuntu Members, from December 20th on, to take a break (with the advisement of Lubuntu Team Lead and Ubuntu Community Council Member Thomas Ward). People who know my leadership style understand that I very rarely put my foot down firmly without accepting questions; I am happy to be wrong, and am thrilled at the opportunity to accept constructive criticism. That being said, I did not want to lose the community we have worked so hard to build. I instructed contributors that this is not as hard of an ask as the usual six month "take a weekend off," but they should not feel pressured to do any significant work over that time. Thankfully, the team came back after the break. That being said, I would be negligent if I did not address the reason as to *why* a break was declared. If it isn't obvious by now, I care about my team, and I care about both Lubuntu and Ubuntu, quite a bit. *We need to communicate and work together better.* The Ubuntu Code of Conduct explicitly affords **any** contributor, **regardless** of their employment status, the right to carry out **any** part of the work with the Ubuntu name on it. I do not plan on invoking the Community Council here, I do not plan on being angry at anyone, and I especially do not plan on bikeshedding about what *is* or *isn't* actually an issue (especially with the ones I just linked). What I'm honestly asking is, please, can we do better here? Can we actually *talk* to one another, and remember that collaboration is the answer? Thank you for your time, consideration, and energy on this issue. Much of this work is thankless, so let me be the one to say: Thank You, Ubuntu Technical Board. We would not be here without you. [1] https://launchpad.net/~lubuntu-dev/+members#active [2] https://launchpad.net/~lubuntu-members/+members#active [3] https://lubuntu.me/links/ [4] https://discourse.lubuntu.me/ [5] https://manual.lubuntu.me/stable/ [6] https://manual.lubuntu.me/lts/ [7] https://lubuntu.me/downloads/ [8] https://lubuntu.me/blog/ [9] https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2046844 [10] https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/2047705 Warm regards, -- Simon Quigley si...@tsimonq2.net tsimonq2 on LiberaChat and OFTC @tsimonq2:ubuntu.com on Matrix 5C7A BEA2 0F86 3045 9CC8 C8B5 E27F 2CF8 458C 2FA4 smime.p7m Description: smime.p7m -- Ubuntu-release mailing list Ubuntu-release@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-release
SRUs and Notifications: Speeding up the SRU Process
Hello Stable Release Updates Team! Over the course of the Ubuntu Summit, I attended a talk by Andreas regarding "the perfect SRU." I was incredibly excited to attend this, so I could ask clarifying questions about specific elements of the process. I brought up an idea that Robie suggested I forward here, which is regarding older SRUs. A major point in the presentation was regarding SRUs which aren't verified in time. Often times, despite our best intentions, Launchpad bug notifications get missed. The vast majority of the time (from what I'm hearing), a simple ping is all that's needed to progress the SRU and get it ready for GA. My suggestion is this: let's have nag emails like Britney gives out. I know what you're thinking: more emails are a bad idea. Usually I would agree. That being said, valid Stable Release Updates have an inherent value to the end user. These are the updates which make the experience better, align actual functionality with expectations in a non-intrusive way, and keep the user secure. I would argue email updates around SRUs are *more* important than Britney notifications, simply in the way of user impact. *I propose that some piece of tooling [standalone, or I'm taking suggestions for existing places] shall notify both the uploader/sponsor and the bug reporter via email once a week until the SRU is fully verified, once accepted in -proposed.* This will have a wider impact on the velocity of SRUs. In the short-term, this means more work for the SRU team, given everyone is now reminded of their SRUs (and thus, a lot will come in at once). This will eventually average out (I estimate over the course of a month) to the point where we have a minimal "pending SRUs" table, and higher velocity for SRUs, benefiting both our users and developers. Please let me know what your thoughts are, otherwise I will get started on some code. Thank you for your time, -- Simon Quigley si...@tsimonq2.net tsimonq2 on LiberaChat and OFTC @tsimonq2:linuxdelta.com on Matrix 5C7A BEA2 0F86 3045 9CC8 C8B5 E27F 2CF8 458C 2FA4 OpenPGP_signature.asc Description: OpenPGP digital signature -- Ubuntu-release mailing list Ubuntu-release@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-release
Ubuntu Studio 22.04.1 and Secure Boot
Hello, This email is meant to provide an update on Ubuntu Studio's Secure Boot situation in 22.04.1. Currently, UEFI Secure Boot installs fail with Ubuntu Studio 22.04 due to the inclusion of the v4loopback DKMS module, which Erich intends to remove from the seed in order to fix this bug. In #ubuntu-release I was reading scrollback from Erich and Łukasz, and there seems to be an issue with germinate grabbing that dependency despite removing it in the seed post-release. Iain Lane chimed in and pointed me to this line[1] in germinate which grabs those packages. I have to agree, it's an impressive line of code. I am willing and able to do the vast majority of the work in fast-tracking this through. However, I am in unfamiliar territory since I do not have SSH access to the server to just take a peek at logs. In terms of testing it, I'd like someone from Canonical to provide technical advice on how to properly solve this. Iain (while his feedback was very useful), did note he may be rusty. As for why this is coming up *now* in the first place, I don't have the slightest clue. In the year 2022, flavors need to at least smoke test *once*, *especially* for an LTS release, to ensure Secure Boot works. Look, I get it, flavor teams may be short-staffed, some more than others, but we really need to take a look at our QA processes as the Ubuntu project to ensure something basic like this is caught in every flavor. (Yes, I'm volunteering to write the ISO QA tests.) It's embarrassing, as a fellow Ubuntu Flavor RM, that something like this was not caught and brought to the attention of the Release Team *immediately*. This isn't personal, I'm not trying to roast anyone in particular, but come on everyone, we really need to do better here. I'll link Lubuntu's thorough test suite here[2], and I would suggest other flavors take our example. Despite my personal regrets on how this should have been handled, we have two days. Let's focus on this first, and we can bikeshed on QA processes afterwards. [1] https://git.launchpad.net/livecd-rootfs/tree/live-build/auto/config#n132 [2] https://phab.lubuntu.me/w/release-team/testing-checklist/ Thanks, -- Simon Quigley si...@tsimonq2.net tsimonq2 on LiberaChat and OFTC @tsimonq2:linuxdelta.com on Matrix 5C7A BEA2 0F86 3045 9CC8 C8B5 E27F 2CF8 458C 2FA4 OpenPGP_signature Description: OpenPGP digital signature -- Ubuntu-release mailing list Ubuntu-release@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-release
Re: Issue with Manual ISO Rebuilds
Here you are: https://bugs.launchpad.net/ubuntu-cdimage/+bug/1980410 On 6/30/22 05:49 AM, Lukasz Zemczak wrote: Hey Simon! Interesting. Can you fill a bug under the https://bugs.launchpad.net/ubuntu-cdimage/ project? I'll investigate it now, since I think the rebuild gets queued but then something dies further in rebuild-requests. But a bug would be a welcome addition anyway. Cheers, On Thu, 30 Jun 2022 at 12:30, Simon Quigley wrote: Hello, Since Ubuntu Studio ran into this issue today, I figured I'd ask the question so we can get this fixed. I can file a bug, just let me know where. When an ISO rebuild is occurring, and it *fails*, until the next daily cron run for the ISO, it can not be manually rebuilt from the ISO QA tracker. Steps to reproduce: 1. Include a package on a daily ISO which fails to install for some reason (duplicate files may be an example). 2. Let the daily ISO cron run and watch it fail. 3. Try to trigger a manual rebuild from the ISO QA tracker. Could someone at Canonical please provide some insight as to what is happening on the server-side, perhaps providing some logs? Thanks. -- Simon Quigley si...@tsimonq2.net tsimonq2 on LiberaChat and OFTC @tsimonq2:linuxdelta.com on Matrix 5C7A BEA2 0F86 3045 9CC8 C8B5 E27F 2CF8 458C 2FA4 -- Ubuntu-release mailing list Ubuntu-release@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-release -- Simon Quigley si...@tsimonq2.net tsimonq2 on LiberaChat and OFTC @tsimonq2:linuxdelta.com on Matrix 5C7A BEA2 0F86 3045 9CC8 C8B5 E27F 2CF8 458C 2FA4 OpenPGP_signature Description: OpenPGP digital signature -- Ubuntu-release mailing list Ubuntu-release@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-release
Issue with Manual ISO Rebuilds
Hello, Since Ubuntu Studio ran into this issue today, I figured I'd ask the question so we can get this fixed. I can file a bug, just let me know where. When an ISO rebuild is occurring, and it *fails*, until the next daily cron run for the ISO, it can not be manually rebuilt from the ISO QA tracker. Steps to reproduce: 1. Include a package on a daily ISO which fails to install for some reason (duplicate files may be an example). 2. Let the daily ISO cron run and watch it fail. 3. Try to trigger a manual rebuild from the ISO QA tracker. Could someone at Canonical please provide some insight as to what is happening on the server-side, perhaps providing some logs? Thanks. -- Simon Quigley si...@tsimonq2.net tsimonq2 on LiberaChat and OFTC @tsimonq2:linuxdelta.com on Matrix 5C7A BEA2 0F86 3045 9CC8 C8B5 E27F 2CF8 458C 2FA4 OpenPGP_signature Description: OpenPGP digital signature -- Ubuntu-release mailing list Ubuntu-release@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-release
Release Candidate (and testable!) Eoan Ermine builds ready to test
Hello, It's that time again. Eoan Final builds should now be available on the ISO QA tracker[1]. These builds are not final; we're still waiting on a few more fixes, a few things to migrate, etc. Neither base-files or the ISO labels are updated yet, so please don't file bugs about those. What there are, however, are "close enough" for people to be testing in anger, filing bugs, fixing bugs, iterating image builds, and testing all over again. So, please, don't wait until Wednesday night to test, testing just before release is *TOO* *LATE* to get anything fixed. Get out there, grab your favorite ISO (if you don't have a favorite, grab them all), beat it up, find bugs, report bugs, escalate bugs, fix bugs, respin (if you're a flavor lead with access), and test, test... And test. Did I mention testing? Please[2] test. As a reminder, we are in Final Freeze, as well as Feature Freeze. Unseeded packages are still more or less a free-for-all, but please verify your uploads first, and ask yourself whether the state currently in the archive is good enough, or if your shiny new bugfix can wait for an SRU/the Furious Falcon. [1] http://iso.qa.ubuntu.com/qatracker/milestones/407/builds [2] Please. Pretty please? On behalf of the Ubuntu Release Team, -- Simon Quigley tsimo...@ubuntu.com tsimonq2 on freenode and OFTC 5C7A BEA2 0F86 3045 9CC8 C8B5 E27F 2CF8 458C 2FA4 signature.asc Description: OpenPGP digital signature -- Ubuntu-release mailing list Ubuntu-release@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-release
Removing Qt 4 from Ubuntu before the 20.04 release
Hello, I would like to completely remove Qt 4 from the Ubuntu archive before the 20.04 release. This includes all of KDE 4 and dependencies. The Debian Qt/KDE Team (which I am a part of) is raising the status of the Qt 4 removal bugs to RC[1], and since the Qt 6 work is starting upstream in the dev branch in the coming months, now is the time for Qt 4 to go. My timeline for this is to change all of the bugs filed to ask people to port[2] to removal bugs, and go over the list of Qt 4 reverse dependencies one last time, so the removal can be done at the beginning of the 20.04 cycle before the archive opens. This would make 19.10 the last release with Qt 4. Flavors, please check if Qt 4 is on your ISO, and if it is, make plans to remove it as soon as you can. Please hop in #ubuntu-qt if you would like help porting your favorite application. Does anyone object to this plan? [1] https://alioth-lists.debian.net/pipermail/pkg-kde-talk/2019-August/002920.html [2] https://bugs.launchpad.net/ubuntu/+bugs?field.tag=qt4-removal -- Simon Quigley tsimo...@ubuntu.com tsimonq2 on freenode and OFTC 5C7A BEA2 0F86 3045 9CC8 C8B5 E27F 2CF8 458C 2FA4 signature.asc Description: OpenPGP digital signature -- Ubuntu-release mailing list Ubuntu-release@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-release
Release Candidate (and testable!) Disco Dingo builds ready to test (hint hint!)
Hello, Disco Final builds should now be available on the ISO QA tracker[1]. These builds are not final. We're still waiting on a few more fixes, a few things to migrate, etc. Neither base-files or the ISO labels are updated yet, so please don't file bugs about those. What there are, however, are "close enough" for people to be testing in anger, filing bugs, fixing bugs, iterating image builds, and testing all over again. So, please, don't wait until Wednesday night to test, testing just before release is *TOO* *LATE* to get anything fixed. Get out there, grab your favorite ISO (if you don't have a favorite, grab them all), beat it up, find bugs, report bugs, escalate bugs, fix bugs, respin (if you're a flavor lead with access), and test, test... And test. Did I mention testing? Please[2] test. [1] http://iso.qa.ubuntu.com/qatracker/milestones/403/builds [2] Please. Pretty please? -- Simon Quigley tsimo...@ubuntu.com tsimonq2 on freenode and OFTC 5C7A BEA2 0F86 3045 9CC8 C8B5 E27F 2CF8 458C 2FA4 signature.asc Description: OpenPGP digital signature -- Ubuntu-release mailing list Ubuntu-release@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-release
Re: Ubuntu 16.04.6 RC images for testing
Hello Łukasz, thanks for the notice on this. Lubuntu will participate in this milestone. Thanks! -- Simon Quigley tsimo...@lubuntu.me tsimonq2 on freenode and OFTC 5C7A BEA2 0F86 3045 9CC8 C8B5 E27F 2CF8 458C 2FA4 signature.asc Description: OpenPGP digital signature -- Ubuntu-release mailing list Ubuntu-release@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-release
Sunsetting i386
Full announcement is here: https://lubuntu.me/sunsetting-i386/ The short version is that Lubuntu 19.04+ will no longer be released on the i386 architecture. -- Simon Quigley tsimo...@lubuntu.me tsimonq2 on freenode and OFTC 5C7A BEA2 0F86 3045 9CC8 C8B5 E27F 2CF8 458C 2FA4 signature.asc Description: OpenPGP digital signature -- Ubuntu-release mailing list Ubuntu-release@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-release
Patch Pilot/+1 Vanguard Report for October 9th
Hello, I decided it would be a good idea to start with the proposal Mathieu laid out in his email to ubuntu-devel[1] by taking some time to go through the sponsorship queue and cosmic-proposed. I remember that Daniel Holbach would send reports to one of these mailing lists, so I'm going to do the same. Here's what I worked on during my shift: Sponsorship and review: - Reviewed the initramfs-tools-devices package and left some feedback. - https://pad.lv/1788601 - Sponsored an SRU patching ntpsec's AppArmor profile. - Requested feedback on IRC from Seth Arnold and he agreed with the patch. - https://pad.lv/1788102 - Unsubscribed the Sponsors Team from the apt-btrfs-snapshot improvement bug and directed the reporter to perhaps help submit changes to Debian. - https://pad.lv/1778256 - Asked for a debdiff on the telepathy-mission-control-5 patch which modifies the apparmor profile to make purple-telegram work. - https://pad.lv/1708375 - Unsubscribed the Sponsors Team from the ubuntukylin-wallpapers sponsorship bug which I sponsored a few days ago. - https://pad.lv/1791416 FTBFS fixing: - libfm-qt was FTBFS on i386 and armhf due to some MISSING symbols which I took care of. - https://launchpad.net/ubuntu/+source/libfm-qt/0.13.1-5ubuntu6 Proposed Migration investigations: - libmongodb-perl isn't migrating because it adds a build and runtime dependency on libbson-xs-perl, which is fine on build time because it's an arch:all build, but since libbson-xs-perl is FTBFS on s390x because of tests, the libmongodb-perl autopkgtest can't pull in the dependency. I wanted to keep this to an hour and I had already spent some time dealing with the IRC netsplit that had occurred, so I cut it short there. I would encourage other Ubuntu Developers, Canonical employees or not, to pick up a shift here or there to help keep the queues at a manageable level. Right now we're down to 355 packages in cosmic-proposed with an average age of 86 days, the sponsorship queue is down to 35 items, and even after the release is done, we can probably get those down lower with enough eyes. This was somewhat spontaneous but my plan is to pick up a shift every week or so, barring life getting in the way. Join me! [1] https://lists.ubuntu.com/archives/ubuntu-devel/2018-September/040501.html -- Simon Quigley tsimo...@ubuntu.com tsimonq2 on freenode and OFTC 5C7A BEA2 0F86 3045 9CC8 C8B5 E27F 2CF8 458C 2FA4 signature.asc Description: OpenPGP digital signature -- Ubuntu-release mailing list Ubuntu-release@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-release
Re: Adding packages to desktop-common
Hello, On 09/18/2018 02:42 AM, Steve Langasek wrote: > I've tweaked the language on > https://wiki.ubuntu.com/SeedManagement/AddingPackagesToDesktopCommon to > taste. Please review and let me know if you object to any of my changes > (which are meant to be editorial only). > > If you agree this is still what's intended, I will go ahead and land your > MP. Thanks, the edits look good to me. Please proceed. -- Simon Quigley tsimo...@ubuntu.com tsimonq2 on freenode and OFTC 5C7A BEA2 0F86 3045 9CC8 C8B5 E27F 2CF8 458C 2FA4 signature.asc Description: OpenPGP digital signature -- Ubuntu-release mailing list Ubuntu-release@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-release
Finding better solutions for noting problems with packages in devel-proposed
Hello, As someone who occasionally goes through the backlog on update_excuses.html to try and find packages which could potentially migrate, I find myself revisiting some packages and wanting to note my findings somewhere that can't be easily spotted by using the Britney output, such as somewhat complex Node.js dependency trees. It would be good to have the ability to note these sort of findings somewhere, such as an Etherpad or a wiki page so someone else (or myself a month or more down the road) doesn't have to waste the time. Here's a bug which relates: https://bugs.launchpad.net/britney/+bug/1683749 But at this point we're filing bugs for packages which haven't migrated, and people could potentially forget once they have migrated. Has something like this ever been considered? If not, does anyone object to me setting up something under our Etherpad instance to coordinate? Thanks. -- Simon Quigley tsimo...@ubuntu.com tsimonq2 on freenode and OFTC 5C7A BEA2 0F86 3045 9CC8 C8B5 E27F 2CF8 458C 2FA4 signature.asc Description: OpenPGP digital signature -- Ubuntu-release mailing list Ubuntu-release@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-release
Re: Adding packages to desktop-common
Hi Steve, Thanks for the feedback on this. I agree with the points you stated, and after discussing with other flavor representatives to make sure we are in agreement, I have adjusted the proposal. Additionally, I have created a merge proposal against the platform seed which, when merged, marks that this has been ratified: https://code.launchpad.net/~tsimonq2/ubuntu-seeds/+git/platform-add-policy-desktop-common/+merge/348795 Thanks again. -- Simon Quigley tsimo...@ubuntu.com tsimonq2 on freenode and OFTC 5C7A BEA2 0F86 3045 9CC8 C8B5 E27F 2CF8 458C 2FA4 signature.asc Description: OpenPGP digital signature -- Ubuntu-release mailing list Ubuntu-release@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-release
Adding packages to desktop-common
Hello, I have drafted a proposal for adding packages to the desktop-common seed. This would be useful to ensure that everybody involved in shipping the contents of the seed agrees on what's in it. Here are the main points of this proposal: - If a package is going to be included, an email should be sent to ubuntu-release with some information on what it is, why we need it, if there are any issues with it, and who is responsible for the package. - An aging period of one week should be used to make sure there are no objections to a package's inclusion. If this needs to be waived, the person proposing its inclusion should state so on the mailing list, and feel free to proceed. - If anyone opposes during or after the aging period, they should work out any concerns with the person proposing it and/or the people responsible for the package. If issues can't be worked out, we can't include it. (If the party opposing it goes MIA, the proposal should be re-sent to the mailing list.) - If there's no objections, it can be added, provided a link to the proposal is in the commit message. Here is the full text of the proposal: https://wiki.ubuntu.com/SeedManagement/AddingPackagesToDesktopCommon Let me know if you have any questions, but otherwise I will be available during the next Technical Board meeting. Thanks. -- Simon Quigley tsimo...@ubuntu.com tsimonq2 on freenode and OFTC 5C7A BEA2 0F86 3045 9CC8 C8B5 E27F 2CF8 458C 2FA4 signature.asc Description: OpenPGP digital signature -- Ubuntu-release mailing list Ubuntu-release@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-release
Re: Flavours - and talking to each other
Hello, On 05/10/2018 03:02 PM, flocculant wrote: > Up to now, about the only contact we all have with each other is when we > needed to respond to a "Who's taking part in this milestone" mails. > > Sometimes if someone had an issue they might talk to a flavour that used > the same package or the like. Xubuntu often talked to Martin Wimpress > for instance. > > I'm wondering if we all need to have some talking shop available to us - > we could use e-mail, but then what list? Thanks for bringing this up! Email might not be the best place. > We could have meetings - but that sounds to me a bit too onerous - the > likely place for that would be IRC - then we have timezones to deal with. Even if it's not frequently used, I've gone ahead and created #ubuntu-flavors on freenode. It'd be good if representatives from each flavor would be there. Even if it's just for informal discussion, I think having an IRC channel is a good idea. > We do now have https://community.ubuntu.com - we could set up a Category > there - Flavour discussions (or something) and people could start > inter-flavour discussions as topics came to them. I also think this is a really good idea for formally proposing things. Thanks again! -- Simon Quigley tsimo...@ubuntu.com tsimonq2 on freenode and OFTC 5C7A BEA2 0F86 3045 9CC8 C8B5 E27F 2CF8 458C 2FA4 signature.asc Description: OpenPGP digital signature -- Ubuntu-release mailing list Ubuntu-release@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-release
Dropping Lubuntu Next and no-follow-recommends
Hello Release Team, https://code.launchpad.net/~tsimonq2/ubuntu-cdimage/drop-lubuntu-next/+merge/345064 and https://code.launchpad.net/~tsimonq2/livecd-rootfs/drop-lubuntu-next/+merge/345065 should be all that's required to stop Lubuntu Next builds and drop the workarounds for no-follow-recommends. Lubuntu Next is now Lubuntu, and old Lubuntu (LXDE) is referred to as Lubuntu Classic. Seed changes have been made to reflect that. Let me know if I forgot anything or if there's still anything to do. We aren't dropping 32-bit yet, but are considering that, and I'll propose an MP if that's decided on. Thanks. -- Simon Quigley tsimo...@lubuntu.me tsimonq2 on freenode and OFTC 5C7A BEA2 0F86 3045 9CC8 C8B5 E27F 2CF8 458C 2FA4 signature.asc Description: OpenPGP digital signature -- Ubuntu-release mailing list Ubuntu-release@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-release
Migrating all seeds to Git
Hello, As some of you know, a project that I took on for Lubuntu in the 18.04 cycle was to migrate our seeds to Git (and to get the necessary tooling bits in place to cope for that). I spoke to Adam Conrad from the Release Team this afternoon, and we agreed that all of the Ubuntu and flavor seeds should migrate to Git before the Cosmic release cycle progresses too far. This would mean that instead of having individual Bazaar branches, there would be one Git repository per flavor, which has different branches for each release, and the EOL releases would be moved to a different (yet similarly-named) Git repository. The old Bazaar branches would be deleted. I wrote a wiki page[1] on how to migrate flavor seeds to Git, feel free to edit the page if I missed anything. Of course, people are encouraged to convert their seeds sooner rather than later, but the goal is to convert all non-converted seeds to Git in one week's time (the afternoon (US/Canada time) of May 8th). Please respond here or let me know if you would not like to proceed with this for the team you represent. No work is required for teams, with the exception of adjusting local clones and custom workflows should they exist. Thanks, and let me know if you have any questions. [1] https://wiki.ubuntu.com/Germinate/ConvertingToGit -- Simon Quigley tsimo...@ubuntu.com tsimonq2 on freenode and OFTC 5C7A BEA2 0F86 3045 9CC8 C8B5 E27F 2CF8 458C 2FA4 signature.asc Description: OpenPGP digital signature -- Ubuntu-release mailing list Ubuntu-release@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-release
Re: Re-evaluating Ubuntu's Milestones
Hello, On 04/22/2018 01:40 AM, Tim wrote: > Obviously Ubuntu GNOME no longer builds ISO's however I would like to > chip in on this discussion with a few thoughts based on past experience. > Feel free to do with them what you wish, its not meant to be criticism > in any way of the current proposal, but more just something to think > about. Sorry I didnt reply earlier, just haven't had the spare time! Thanks for taking the time to reply. > First my gut feeling is your going to see less community participation > because there is no tangible outcome, obviously this will vary depending > on the flavours community, some my do better, some may do worse. The goal is to have established testing weeks increase the number for *everyone* while lessening the burden for everyone. > From a technical perspective having the archive frozen was quite useful, > it allows you to focus on a fixed target, rather than getting distracted > by a moving target that may well introduce further bugs. Actually, I have typically seen more bugs *fixed* immediately after a milestone release than introduced. Also, if we didn't have to spend our time working hard to release a product (Alphas and Beta 1), we could focus on improving and refining QA (both automated and manual) and spend time on that instead. > LIkewise for > giving the flavour leads control over re-spins rather than depending on > daily builds. Flavor leads do have control over respinning images, but they don't have control over stopping them (maybe just pressing the "disable" button?); we have yet to hear back from the Ubuntu Release Team on that. > I would also agree at times, that is was somewhat > restrictive at times, but a semi-frozen archive where flavours had more > control over the flow of packages, could lessen that (auto-accept > flavour uploads perhaps, that don't overlap other flavours?). This would make the ISOs stale, thus proving the point of the images being "stale on arrival". ;) > I think > traditionally there have been too many milestones in a cycle (perhaps > somewhat biased by GNOME's late release cycle), however I still think > the milestones serve an important purpose. If Ubuntu GNOME were still > spinning ISO's, I'd probably advocate for a more hybrid model, use the > more informal testing 'weeks' early in the cycle, then one beta and the > RC Milestones. This is precisely what I'm proposing. Get rid of Alpha 1, Alpha 2, and Beta 1, then rename "Final Beta" to just "Beta". Then we have the RCs, which aren't really a milestone. > As for the automated testing, I think is important, however my > recollections of so many milestone releases dealing with somewhat corner > case installer bugs, wonder how you will get 100% test coverage. Also > for some flavours the work maintaining these test cases may end up being > as much work as co-ordinating milestone releases. I would probably > recommend getting the automated testing in place before changing things > too drastically. I disagree; while putting in automated testing is definitely something that I believe in making a priority, we don't need to block on change for that. The goal is to "set it and forget it" (which, with the nature of how these tests are designed, can be done in that way), so while it may involve some initial investment, I think the return far exceeds the time spent. -- Simon Quigley tsimo...@ubuntu.com tsimonq2 on freenode and OFTC 5C7A BEA2 0F86 3045 9CC8 C8B5 E27F 2CF8 458C 2FA4 signature.asc Description: OpenPGP digital signature -- Ubuntu-release mailing list Ubuntu-release@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-release
Re: Re-evaluating Ubuntu's Milestones
Hello, On 04/21/2018 04:15 AM, flocculant wrote: > One quick question here - imagine that :) > > Given that we all (apparently) find it hard to get people testing during > the 3 days we currently get at milestone's - why are we carrying on with > that same tight schedule? You'll know the way this happens - it's the > end of the testing session and suddenly someone is asking for help > looking at their images for some reason. > > If we are going to just organise sections of time amongst ourselves > during these new periods - why not do away with "weeks" and actually > have a week - a real week. If we can't manage to organise amongst > ourselves for longer than a couple of days then I think we should all > pack up and do something else ;) That works for me. We can work out the fine specifics when we get closer (I have a couple of things in mind that I'd like to iron out first), but I'm not opposed to making it weeks instead of "weeks". > If not, then all that's really been accomplished here is making life > easier for Canonical (not that I disagree with us doing that I hasten to > add), we as flavours are gaining nothing. This isn't really making things easier for just the Ubuntu Release Team. Even if we still kept to a strict schedule, we don't have to worry about people testing with old installs (see my point to Oliver about the "pristine" ISOs). Thanks for the email. -- Simon Quigley tsimo...@ubuntu.com tsimonq2 on freenode and OFTC 5C7A BEA2 0F86 3045 9CC8 C8B5 E27F 2CF8 458C 2FA4 signature.asc Description: OpenPGP digital signature -- Ubuntu-release mailing list Ubuntu-release@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-release
Re: Ubuntu Studio Release Manager
Hello, On 04/21/2018 10:03 AM, er...@ericheickmeyer.com wrote: > Hi all, > > I’ve already introduced myself on IRC, but I’m here to let you know that I’m > the new Ubuntu Studio release manager. You can find me on launchpad at > https://launchpad.net/~eeickmeyer, and on IRC as ErichEickmeyer. Welcome. :) Please don't hesitate to reach out if you have any questions! Have a nice day, -- Simon Quigley tsimo...@ubuntu.com tsimonq2 on freenode and OFTC 5C7A BEA2 0F86 3045 9CC8 C8B5 E27F 2CF8 458C 2FA4 signature.asc Description: OpenPGP digital signature -- Ubuntu-release mailing list Ubuntu-release@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-release
Re: Re-evaluating Ubuntu's Milestones
Happy Release Week! I do not believe there have been any -1s to this proposal from any flavor, nor from the Release Team, so I think it's time to move forward with it. In summary, what will now happen from here on out is that opt-in milestones will be discontinued in favor of testing "weeks" (Tuesday through Thursday). I can organize the testing weeks for the 18.10 cycle (so we can get a process going), but from the 19.04 cycle and on, representatives (probably Release Managers) from any active flavor can (and should!) organize these testing weeks. Additionally, I will look into the automated testing Steve brought up shortly after the 18.04 release, with the goal being to adopt that sooner rather than later. I'll write a follow-up email to ubuntu-release once I have something to show for that. Thanks everyone! -- Simon Quigley tsimo...@ubuntu.com tsimonq2 on freenode and OFTC 5C7A BEA2 0F86 3045 9CC8 C8B5 E27F 2CF8 458C 2FA4 signature.asc Description: OpenPGP digital signature -- Ubuntu-release mailing list Ubuntu-release@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-release
Re: Call for confirmation of LTSness of flavours for bionic
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 I represent Lubuntu, and I confirm that we intend to support Lubuntu 18.04 for three years, and the packages that comprise Lubuntu Next for nine months. - -- Simon Quigley tsimo...@lubuntu.me tsimonq2 on freenode and OFTC 5C7A BEA2 0F86 3045 9CC8 C8B5 E27F 2CF8 458C 2FA4 -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEXHq+og+GMEWcyMi14n8s+EWML6QFAlrR340ACgkQ4n8s+EWM L6R9VQ/+PxaA3Olum4AKueuqi8LsAAWalOWKiSQc63SBURsO3eqBfc4cDCe0vPH6 oYCnPdmUvbChlNWTkaVMGNtDrvy3S9Zx1p+6yCx8l9N3DRaWqI4YOkdHkBZNwSun nn7U3baqHSGSCcuDThu/vhYy//uVkPiotJFJkclOMEQI/YTQSMVCSdaWkHohSX5J XCR6zsRQ1z2ePvr1NWfcY8nW24I/elZ0YfqhfFKlRc7tmFXR3UmWial5D3m63BR1 N9YIA1yGYlH6biqUH2TKSx5GnJhW2YN3Stu3qdBhClsPZd4IvcbjFlMxDr1VJtub eEDUh6TJVESMmCWeC6AbC4s1NkFsFcftPVcqUX783SOHoiFYYdvMjpUu1aQqy7O6 BQy7u+bfKaijB+tliB/psC6aZpTQx7ul2heCtHtxEofBPhzlzcTzXFfuzE4tCEcw hPh8Eh0U5/d59ALkMnRWmVR5VeVC0duIX7zqJHjV3ymXBrHynKfzaSTv1svngP+e WK/t8zzE6lKqFXhGMxApfp6pdBKZac52a89tSxbaFlk4A61KGtznYWQfTEqmpn3N g4jdmXtr75UNY3/8uXVCcta+mz5Izd142OnSYW5KllTCbUhosCQiP1X63BFA87Xk lhslMFl45tCHVACXEU0BP0PQQCOwT6jMGavDrWj0wPnCY1Zt1O4= =GYz1 -END PGP SIGNATURE- -- Ubuntu-release mailing list Ubuntu-release@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-release
Re: Re-evaluating Ubuntu's Milestones
Hello, On 04/09/2018 03:13 PM, Steve Langasek wrote: > The one other value milestone images provide is to give a "known good" image > to install the development release from. We have solved this for Ubuntu > Desktop and Server by having automated tests that gate the promotion of an > image build to "current". I would strongly encourage flavors to collaborate > around this automation, instead of continuing to rely on a heavy-weight > manual test process that leaves the "known good" image stale for weeks at a > time. > > Code for this automation lives here: > > https://code.launchpad.net/~ubuntu-test-case-dev/ubuntu-test-cases/desktop > > If there is interest from flavors in having this image gate, I would be > willing to argue for Canonical hosting of the test infrastructure, as > necessary. > > And if there *isn't* interest from flavors in doing this, well, I also don't > think that should block on that as a reason to carry on with the existing > milestone process, which I think is a very inefficient use of everyone's > time. I think this is an excellent idea which would be great to look into for the 18.10 cycle. Count Lubuntu in. > So to summarize, I think the right path forward is: > > - discontinue all opt-in milestones for 18.10 and beyond >- implicitly discontinuing the matching milestone freezes > - coordinate a cadence of "testing weeks", organized by the flavor leads >(i.e.: requires no involvement from ubuntu-cdimage or ubuntu-release in >order to drive to success) > - at the flavor teams' discretion, implement automated QA gating of daily >image promotions Great, I think we're on the same page here. :) -- Simon Quigley tsimo...@ubuntu.com tsimonq2 on freenode and OFTC 5C7A BEA2 0F86 3045 9CC8 C8B5 E27F 2CF8 458C 2FA4 signature.asc Description: OpenPGP digital signature -- Ubuntu-release mailing list Ubuntu-release@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-release
Re: Re-evaluating Ubuntu's Milestones
Hello Oliver, On 2018-04-09 03:30, Oliver Grawert wrote: well, apart from actual installer fixes, your users should get all these fixes through package updates anyway ... Right, which is another point for getting rid of these extra milestones, in my opinion. One thing that the other pro/con responses did not cover yet but that should not be underestimated is the promotional aspect of milestones ... You typically get press coverage for such pre-releases and will likely attract more testers. Not really, actually. In my experience, testers are present when there is an occasion to test them, regardless of putting a name to it or releasing an ISO. I could see your point if my proposal was to get rid of the milestones entirely with no replacements, but in this case, having the testing week once a month would attract press coverage as well. Why? Because milestones in all reality are just a fancy name to slap on an ISO that will most likely be stale the next day. You then get people installing from these ISOs and potentially even reporting old bugs. The unfortunate reality of this press coverage is that you could pick an ISO any day of the month and call it "beta," and just because it has that name on it means that people will install it because of the appeal of the name. Despite the positive press that comes from the associated announcements (that can always be made regardless, which is what Lubuntu has started doing[1]), in a technical sense, I would even consider it *bad* for people to install using these ISOs. The coordinated testing weeks would allow for there still to be positive press coverage (and maybe announcements resulting from cross-team collaboration during these times) while not having the downsides of a blessed image when the archive isn't in a decently stable state. [1] https://lubuntu.me/category/newsletter/ -- Simon Quigley tsimo...@ubuntu.com tsimonq2 on freenode and OFTC 5C7A BEA2 0F86 3045 9CC8 C8B5 E27F 2CF8 458C 2FA4 -- Ubuntu-release mailing list Ubuntu-release@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-release
Re-evaluating Ubuntu's Milestones
buntu.com/DebianImportFreeze [3] https://wiki.ubuntu.com/FeatureDefinitionFreeze [4] https://wiki.ubuntu.com/UserInterfaceFreeze [5] https://wiki.ubuntu.com/DocumentationStringFreeze -- Simon Quigley tsimo...@ubuntu.com tsimonq2 on freenode and OFTC 5C7A BEA2 0F86 3045 9CC8 C8B5 E27F 2CF8 458C 2FA4 signature.asc Description: OpenPGP digital signature -- Ubuntu-release mailing list Ubuntu-release@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-release
Bionic Beaver Alpha 1?
Hello everyone, Is anyone up for an Alpha 1 in the beginning of January? Currently we have January 4th as the date for that, but maybe that needs to be pushed back a week to January 11th, given that people are probably still going to be on vacation (or getting back into things after it, at the least). What does the Release Team think? To get it out of the way (because it comes up every cycle it seems), I still do see the use in an Alpha 1, especially with this being an LTS release, and given the development pace of Lubuntu and Kubuntu (at minimum) thus far in Bionic, it would really help to have an Alpha. I've also signed myself up for checklist tracking for this one, so I just need someone from the Release Team to volunteer to take care of Nusakan and cron job disabling (the normal stuff). (It would be preferrable if the person who volunteers for this lives in the USA or Canada so our timezones aren't drastically different; I've learned that it often doesn't turn out well otherwise.) Lubuntu is a definite yes, but if other flavors would like to participate, please edit this wiki page[1] (or send me an email and I can take care of it) with updated contact information if applicable and the location for your release notes. If a representative from a flavor doesn't respond or edit the wiki page, I'll assume that they aren't participating. Thanks everyone, and happy holidays! [1] https://wiki.ubuntu.com/BionicBeaver/Alpha1 -- Simon Quigley tsimo...@ubuntu.com tsimonq2 on freenode and OFTC 5C7A BEA2 0F86 3045 9CC8 C8B5 E27F 2CF8 458C 2FA4 signature.asc Description: OpenPGP digital signature -- Ubuntu-release mailing list Ubuntu-release@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-release
Re: Artful Aardvark Beta 1?
Hello, On 08/28/2017 06:19 AM, Martin Wimpress wrote: > Hi all, > > I'm currently signed to do checklist tracking for Beta 1 which is due > August 31st. Who is looking to participate? For the record, Ubuntu > MATE is participating. > > To properly keep track of who is and isn't participating please update > the following wiki page as well as replying to this email: > > * https://wiki.ubuntu.com/ArtfulAardvark/Beta1 > > I've assumed that everyone who participated in Alpha 2 is > participating in Beta 1. If that is not the case please update the > wiki accordingly. If your flavour is opting in to Beta 1 then please > make sure the contact information for your release team and the link > to where your release notes will be posted is updated. > > If you don't have access to the wiki, feel free to send me an email or > a ping on IRC (flexiondotorg). > Lubuntu is in. -- Simon Quigley tsimo...@ubuntu.com tsimonq2 on freenode and OFTC 5C7A BEA2 0F86 3045 9CC8 C8B5 E27F 2CF8 458C 2FA4 -- Ubuntu-release mailing list Ubuntu-release@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-release
We Need a Volunteer with access to Nusakan for Alpha 2
Hello! For Alpha 2, it's been a bit of a slow start as I've been working with Dustin Krysak doing checklist tracking, but it seems that we don't have anyone who has access to Nusakan interested in helping us out. We also need to have an archive block set and images spun up. Are there any volunteers that can help us out? -- Simon Quigley tsimo...@ubuntu.com tsimonq2 on freenode and OFTC 5C7A BEA2 0F86 3045 9CC8 C8B5 E27F 2CF8 458C 2FA4 -- Ubuntu-release mailing list Ubuntu-release@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-release
Re: Ubuntu Flavors, check onboard gsettings overrides
Hey Jeremy! > Ubuntu has been customizing onboard's default settings for years. But > now that the package is in sync with Debian, those settings will need > to be moved to the individual flavor's gsettings overrides. Are the only flavors affected the ones on the bug report? -- Simon Quigley tsimo...@ubuntu.com tsimonq2 on freenode and OFTC 5C7A BEA2 0F86 3045 9CC8 C8B5 E27F 2CF8 458C 2FA4 -- Ubuntu-release mailing list Ubuntu-release@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-release
Artful Aardvark Alpha 1 Released!
"Ten billion ants in this world, and I'm having trouble with just one." - Aardvark from The Ant and the Aardvark The first alpha of the Artful Aardvark (to become 17.10) has now been released! This milestone features images for Lubuntu, Kubuntu, and Ubuntu Kylin. Pre-releases of the Artful Aardvark are *not* encouraged for anyone needing a stable system or anyone who is not comfortable running into occasional, even frequent breakage. They are, however, recommended for Ubuntu flavor developers and those who want to help in testing, reporting, and fixing bugs as we work towards getting this release ready. Alpha 1 includes a number of software updates that are ready for wider testing. This is quite an early set of images, so you should expect some bugs. While these Alpha 1 images have been tested and work, except as noted in the release notes, Ubuntu developers are continuing to improve the Artful Aardvark. In particular, once newer daily images are available, system installation bugs identified in the Alpha 1 installer should be verified against the current daily image before being reported in Launchpad. Using an obsolete image to re-report bugs that have already been fixed wastes your time and the time of developers who are busy trying to make 17.10 the best Ubuntu release yet. Always ensure your system is up to date before reporting bugs. Lubuntu: Lubuntu is a flavor of Ubuntu based on LXDE and focused on providing a very lightweight distribution. The Lubuntu 17.10 Alpha 1 images can be downloaded from: * http://cdimage.ubuntu.com/lubuntu/releases/artful/alpha-1/ More information about Lubuntu 17.10 Alpha 1 can be found here: * https://wiki.ubuntu.com/ArtfulAardvark/Alpha1/Lubuntu Also in this milestone is Lubuntu Next, an experimental flavor of Ubuntu based on LXQt and focused on providing a modern, lightweight, Qt-based distribution. The Lubuntu Next 17.10 Alpha 1 images can be downloaded from: * http://cdimage.ubuntu.com/lubuntu-next/releases/artful/alpha-1/ More information about Lubuntu Next 17.10 Alpha 1 can be found here: * https://wiki.ubuntu.com/ArtfulAardvark/Alpha1/LubuntuNext Kubuntu: Kubuntu is the KDE-based flavor of Ubuntu. It uses the Plasma desktop and includes a wide selection of tools from the KDE project. The Kubuntu 17.10 Alpha 1 images can be downloaded from: * http://cdimage.ubuntu.com/kubuntu/releases/artful/alpha-1/ More information about Kubuntu 17.10 Alpha 1 can be found here: * https://wiki.ubuntu.com/ArtfulAardvark/Alpha1/Kubuntu Ubuntu Kylin: Ubuntu Kylin is a flavor of Ubuntu that is more suitable for Chinese users. The Ubuntu Kylin 17.10 Alpha 1 images can be downloaded from: * http://cdimage.ubuntu.com/ubuntukylin/releases/artful/alpha-1/ More information about Ubuntu Kylin 17.10 Alpha 1 can be found here: * https://wiki.ubuntu.com/ArtfulAardvark/Alpha1/UbuntuKylin If you're interested in following the changes as we further develop the Artful Aardvark, we suggest that you subscribe to the ubuntu-devel-announce list. This is a low-traffic list (a few posts a week) carrying announcements of approved specifications, policy changes, alpha releases and other interesting events. * http://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce A big thank you to the developers and testers for their efforts to pull together this Alpha release! On behalf of Ubuntu Release Team, Simon Quigley -- Ubuntu-release mailing list Ubuntu-release@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-release
Artful Aardvark Alpha 1?
Hello everyone, I'm currently signed up to do checklist tracking for Alpha 1 next week, so I'm wondering, who is participating? If your flavor would like to participate in Alpha 1, in order to properly keep track of who is and who isn't participating (instead of having to sort through emails), I think it would make coordination easier if everyone were to to edit the wiki page: https://wiki.ubuntu.com/ArtfulAardvark/Alpha1 If it has changed, please also update the contact information for your flavor's release team and the link to where your release notes will be. If you don't have access to the wiki, feel free to send me an email or a ping on IRC/Telegram and we can get that sorted out. Thanks! -- Simon Quigley tsimo...@ubuntu.com tsimonq2 on freenode and OFTC 5C7A BEA2 0F86 3045 9CC8 C8B5 E27F 2CF8 458C 2FA4 -- Ubuntu-release mailing list Ubuntu-release@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-release
Zesty Zapus Beta 1 Released
The first beta of the Zesty Zapus (to become 17.04) has now been released! This milestone features images for Kubuntu, Lubuntu, Ubuntu Budgie, Ubuntu GNOME, Ubuntu Kylin, Ubuntu Studio, and Xubuntu. Pre-releases of the Zesty Zapus are *not* encouraged for anyone needing a stable system or anyone who is not comfortable running into occasional, even frequent breakage. They are, however, recommended for Ubuntu flavor developers and those who want to help in testing, reporting, and fixing bugs as we work towards getting this release ready. Beta 1 includes a number of software updates that are ready for wider testing. This is still an early set of images, so you should expect some bugs. While these Beta 1 images have been tested and work, except as noted in the release notes, Ubuntu developers are continuing to improve the Zesty Zapus. In particular, once newer daily images are available, system installation bugs identified in the Beta 1 installer should be verified against the current daily image before being reported in Launchpad. Using an obsolete image to re-report bugs that have already been fixed wastes your time and the time of developers who are busy trying to make 17.04 the best Ubuntu release yet. Always ensure your system is up to date before reporting bugs. Kubuntu: Kubuntu is the KDE based flavor of Ubuntu. It uses the Plasma desktop and includes a wide selection of tools from the KDE project. The Kubuntu 17.04 Beta 1 images can be downloaded from: * http://cdimage.ubuntu.com/kubuntu/releases/zesty/beta-1/ More information about Kubuntu 17.04 Beta 1 can be found here: * https://wiki.ubuntu.com/ZestyZapus/Beta1/Kubuntu Lubuntu: Lubuntu is a flavor of Ubuntu based on LXDE and focused on providing a very lightweight distribution. The Lubuntu 17.04 Beta 1 images can be downloaded from: * http://cdimage.ubuntu.com/lubuntu/releases/zesty/beta-1/ More information about Lubuntu 17.04 Beta 1 can be found here: * https://wiki.ubuntu.com/ZestyZapus/Beta1/Lubuntu Ubuntu Budgie: Ubuntu Budgie is a flavor of Ubuntu featuring the Budgie desktop environment. The Ubuntu Budgie 17.04 Beta 1 images can be downloaded from: * http://cdimage.ubuntu.com/ubuntu-budgie/releases/zesty/beta-1/ More information about Ubuntu GNOME 17.04 Beta 1 can be found here: * https://wiki.ubuntu.com/ZestyZapus/Beta1/UbuntuBudgie Ubuntu GNOME: Ubuntu GNOME is a flavor of Ubuntu featuring the GNOME desktop environment. The Ubuntu GNOME 17.04 Beta 1 images can be downloaded from: * http://cdimage.ubuntu.com/ubuntu-gnome/releases/zesty/beta-1/ More information about Ubuntu GNOME 17.04 Beta 1 can be found here: * https://wiki.ubuntu.com/ZestyZapus/Beta1/UbuntuGNOME Ubuntu Kylin: Ubuntu Kylin is a flavor of Ubuntu that is more suitable for Chinese users. The Ubuntu Kylin 17.04 Beta 1 images can be downloaded from: * http://cdimage.ubuntu.com/ubuntukylin/releases/zesty/beta-1/ More information about Ubuntu Kylin 17.04 Beta 1 can be found here: * https://wiki.ubuntu.com/ZestyZapus/Beta1/UbuntuKylin Ubuntu Studio: Ubuntu Studio is a flavor of Ubuntu configured for multimedia production. The Ubuntu Studio 17.04 Beta 1 images can be downloaded from: * http://cdimage.ubuntu.com/ubuntustudio/releases/zesty/beta-1/ More information about Ubuntu Studio 17.04 Beta 1 can be found here: * https://wiki.ubuntu.com/ZestyZapus/Beta1/UbuntuStudio Xubuntu: Xubuntu is a flavor of Ubuntu based on the Xfce desktop environment. The Xubuntu 17.04 Beta 1 images can be downloaded from: * http://cdimage.ubuntu.com/xubuntu/releases/zesty/beta-1/ More information about Xubuntu 17.04 Beta 1 can be found here: * http://wiki.xubuntu.org/releases/17.04/release-notes If you're interested in following the changes as we further develop the Zesty Zapus, we suggest that you subscribe to the ubuntu-devel-announce list. This is a low-traffic list (a few posts a month or less) carrying announcements of approved specifications, policy changes, alpha releases, and other interesting events. * http://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce A big thank you to the developers and testers for their efforts to pull together this Beta release! On behalf of the Ubuntu Release Team, Simon Quigley -- Ubuntu-release mailing list Ubuntu-release@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-release
Re: Zest Zaphus - Beta 1
Walter Lapchynski pointed out that the timestamps on iso.qa.ubuntu.com don't match up. Here's the current timestamps on all of the products: Kubuntu - 20170220 Lubuntu Desktop - 20170220 Lubuntu Alternate - 20170221.2 Ubuntu Budgie - 20170219 Ubuntu GNOME - 20170219 Ubuntu Kylin - 20170219 Ubuntu Studio - 20170219 Xubuntu - 20170220 I'm aware of the Lubuntu Alternate image respin, as Adam Conrad fixed an unusual build issue with the images and had to respin (thanks Adam!), but this is generally unusual for the other timestamps to be mixed up like this. I also remember that when I added Lubuntu builds to Beta 1, Lubuntu had 20170220 and the rest had 20170219. So what now? Do we respin images or do we keep them as is? Is this a bad thing? -- Simon Quigley tsimo...@ubuntu.com tsimonq2 on freenode and OFTC 5C7A BEA2 0F86 3045 9CC8 C8B5 E27F 2CF8 458C 2FA4 -- Ubuntu-release mailing list Ubuntu-release@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-release
Re: Zest Zaphus - Beta 1
Hello, On 2017-02-17 06:55, flocculant wrote: I see Simon [1] put his name down to sort out this for flavours. Yep. :) Sorry for the late timing on this, Lubuntu is in. -- Simon Quigley tsimo...@ubuntu.com tsimonq2 on freenode and OFTC 5C7A BEA2 0F86 3045 9CC8 C8B5 E27F 2CF8 458C 2FA4 -- Ubuntu-release mailing list Ubuntu-release@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-release
Ubuntu 16.04.2
Hello, I'm just wondering what the progress on preparing the Ubuntu 16.04.2 milestone is. Today I was told on IRC that things were a little bit behind, but when I came home tonight (the night before we're supposed to release), we don't even have anything on iso.qa.ubuntu.com, so while our testers can test the daily images, we aren't sure if this will be the final set of packages shipping in 16.04.2. What's going on here, and am I missing something I should have picked up on? -- Simon Quigley tsimo...@ubuntu.com tsimonq2 on freenode and OFTC 5C7A BEA2 0F86 3045 9CC8 C8B5 E27F 2CF8 458C 2FA4 -- Ubuntu-release mailing list Ubuntu-release@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-release
Zesty Zapus Alpha 2 Released
"Without deviation from the norm, progress is not possible." - Frank Zapus The second alpha of the Zesty Zapus (to become 17.04) has now been released! This milestone features images for Lubuntu, Kubuntu, Ubuntu MATE, Ubuntu Kylin, Ubuntu GNOME, and Ubuntu Budgie. Pre-releases of the Zesty Zapus are *not* encouraged for anyone needing a stable system or anyone who is not comfortable running into occasional, even frequent breakage. They are, however, recommended for Ubuntu flavor developers and those who want to help in testing, reporting and fixing bugs as we work towards getting this release ready. Alpha 2 includes a number of software updates that are ready for wider testing. This is still an early set of images, so you should expect some bugs. While these Alpha 2 images have been tested and work, except as noted in the release notes, Ubuntu developers are continuing to improve the Zesty Zapus. In particular, once newer daily images are available, system installation bugs identified in the Alpha 2 installer should be verified against the current daily image before being reported in Launchpad. Using an obsolete image to re-report bugs that have already been fixed wastes your time and the time of developers who are busy trying to make 17.04 the best Ubuntu release yet. Always ensure your system is up to date before reporting bugs. Lubuntu: Lubuntu is a flavor of Ubuntu based on LXDE and focused on providing a very lightweight distribution. The Lubuntu 17.04 Alpha 2 images can be downloaded from: * http://cdimage.ubuntu.com/lubuntu/releases/zesty/alpha-2/ More information about Lubuntu 17.04 Alpha 2 can be found here: * https://wiki.ubuntu.com/ZestyZapus/Alpha2/Lubuntu Ubuntu MATE: Ubuntu MATE is a flavor of Ubuntu featuring the MATE desktop environment for people who just want to get stuff done. The Ubuntu MATE 17.04 Alpha 2 images can be downloaded from: * http://cdimage.ubuntu.com/ubuntu-mate/releases/zesty/alpha-2/ More information about Ubuntu MATE 17.04 Alpha 2 can be found here: * https://wiki.ubuntu.com/ZestyZapus/Alpha2/UbuntuMATE Ubuntu Kylin: Ubuntu Kylin is a flavor of Ubuntu that is more suitable for Chinese users. The Ubuntu Kylin 17.04 Alpha 2 images can be downloaded from: * http://cdimage.ubuntu.com/ubuntukylin/releases/zesty/alpha-2/ More information about Ubuntu Kylin 17.04 Alpha 2 can be found here: * https://wiki.ubuntu.com/ZestyZapus/Alpha2/UbuntuKylin Kubuntu: Kubuntu is the KDE based flavor of Ubuntu. It uses the Plasma desktop and includes a wide selection of tools from the KDE project. The Kubuntu 17.04 Alpha 2 images can be downloaded from: * http://cdimage.ubuntu.com/kubuntu/releases/zesty/alpha-2/ More information about Kubuntu 17.04 Alpha 2 can be found here: * https://wiki.ubuntu.com/ZestyZapus/Alpha2/Kubuntu Ubuntu GNOME: Ubuntu GNOME is a flavor of Ubuntu featuring the GNOME desktop environment. The Ubuntu GNOME 17.04 Alpha 2 images can be downloaded from: * http://cdimage.ubuntu.com/ubuntu-gnome/releases/zesty/alpha-2/ More information about Ubuntu GNOME 17.04 Alpha 2 can be found here: * https://wiki.ubuntu.com/ZestyZapus/Alpha2/UbuntuGNOME Ubuntu Budgie: Ubuntu Budgie is a flavor of Ubuntu featuring the Budgie desktop environment. The Ubuntu GNOME 17.04 Alpha 2 images can be downloaded from: * http://cdimage.ubuntu.com/ubuntu-budgie/releases/zesty/alpha-2/ More information about Ubuntu GNOME 17.04 Alpha 2 can be found here: * https://wiki.ubuntu.com/ZestyZapus/Alpha2/UbuntuBudgie If you're interested in following the changes as we further develop the Zesty Zapus, we suggest that you subscribe to the ubuntu-devel-announce list. This is a low-traffic list (a few posts a month or less) carrying announcements of approved specifications, policy changes, alpha releases, and other interesting events. * http://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce A big thank you to the developers and testers for their efforts to pull together this Alpha release, and welcome Ubuntu Budgie! On behalf of the Ubuntu Release Team, Simon Quigley -- Ubuntu-release mailing list Ubuntu-release@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-release
Re: Zesty Alpha 2?
We've ended up postponing Alpha 2 to Friday the 27th after Kubuntu had some issues. I should be home by 2 PM Central Time (UTC-6) at the latest that day, so that's when it will probably happen. Please respond if you are not okay with this. -- Simon Quigley tsimo...@ubuntu.com tsimonq2 on freenode and OFTC 5C7A BEA2 0F86 3045 9CC8 C8B5 E27F 2CF8 458C 2FA4 -- Ubuntu-release mailing list Ubuntu-release@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-release
Re: Zesty Alpha 2?
Alright, Ubuntu Kylin and Ubuntu MATE are on the tracker. -- Simon Quigley tsimo...@ubuntu.com tsimonq2 on freenode and OFTC 5C7A BEA2 0F86 3045 9CC8 C8B5 E27F 2CF8 458C 2FA4 -- Ubuntu-release mailing list Ubuntu-release@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-release
Re: Zesty Alpha 2?
We have Alpha 2 images ready for testing. Here are the flavors I have as participating: - Ubuntu Budgie - Lubuntu - Kubuntu (currently FTBFS, working on an issue) - Ubuntu GNOME - Xubuntu (for some reason it's on the tracker, please look into this if this is wrong, which it probably is) Am I missing anyone? -- Simon Quigley tsimo...@ubuntu.com tsimonq2 on freenode and OFTC 5C7A BEA2 0F86 3045 9CC8 C8B5 E27F 2CF8 458C 2FA4 -- Ubuntu-release mailing list Ubuntu-release@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-release
Re: Zesty Alpha 2?
Hi Jeremy, thanks for bringing this up. While I'm still finishing up finals week (and probably should be studying...), I should be back by the afternoon of the 20th. I already put my name down for Beta 1 (open for people who want to do that alongside me or even instead of me, by the way, go right ahead) but I can help out with Alpha 2 as well if nobody else plans on stepping up. I know that Kubuntu and Lubuntu will participate in Alpha 2, we've been sharing some resources lately (some people in both flavors) and we're (pretty much) ready for Alpha 2. Count us both in. Otherwise, who else is in? -- Simon Quigley tsimo...@ubuntu.com tsimonq2 on freenode and OFTC 5C7A BEA2 0F86 3045 9CC8 C8B5 E27F 2CF8 458C 2FA4 -- Ubuntu-release mailing list Ubuntu-release@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-release
Re: Kubuntu 16.10
We're also waiting on an FFe for KDE Applications 16.04.3 (which would then still need an upload by Rohan or someone else). If a release team member has a minute, it would be great if it could be approved: https://bugs.launchpad.net/ubuntu/+source/kdepim/+bug/1625756 Otherwise, I've prepared Plasma 5.7.5 for Rohan to upload tomorrow morning (as agreed in #kubuntu-devel), and then we're just waiting on Scarlett to upload KDE Frameworks 5.26. Thanks Rohan! -- Simon Quigley tsimo...@ubuntu.com tsimonq2 on freenode and OFTC -- Ubuntu-release mailing list Ubuntu-release@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-release
Kubuntu 16.10
Release Team, At the moment, Kubuntu has fallen behind on getting up-to-date KDE applications in the Ubuntu archive due to the lack of developers with permissions to upload to the archive, and we would like some help to ensure that Kubuntu 16.10 ships with up-to-date and tested software. If you weren't aware, KDE releases three (3) different collections of software: 1. KDE Plasma 2. KDE Frameworks 3. KDE Applications Currently, these are the versions of each collection in the archive: 1. KDE Plasma 5.7.2 2. KDE Frameworks 5.24 3. KDE Applications 5.12.3 These are outdated packages, and we would like to update them in order to stay current with the KDE releases. Here are the versions we would like in the archive: 1. KDE Plasma 5.7.5 2. KDE Frameworks 5.26 3. KDE Applications 16.04.3 KDE Plasma 5.7.5 is just a bugfix release, so the regression risk is low. This should be safe to upload. Frameworks and Applications (as well as Plasma) have been tested by our QA team for a week or more now, and we believe they are production ready. Unfortunately, we don't have enough developers to be able to upload these for the Yakkety Yak release at the moment, so we would like some help. Scarlett Clark has agreed to upload KDE Frameworks 5.26, but she is very busy moving and with her job, so we need the rest uploaded. We understand that this is a very unique situation, but in the future, we plan on applying to become Kubuntu Developers (so this can be prevented in the future). We have access to all of the Git repositories Kubuntu uses for development, including all of the PPAs, and we understand the risks in doing this. We will make sure to be around to help if anything were to go wrong (very unlikely) and are able to help with any issues that arise. Would someone either from the community or the Release Team be able to sponsor our uploads? And Release Team, is this acceptable, even with Final Beta Freeze incoming very shortly? Thank you for your time, The Kubuntu "Ninjas" Simon Quigley (tsimonq2 on freenode) Clive Johnston (clivejo on freenode) Rik Mills (acheronuk on freenode) José Manuel Santamaría Lema (santa_ on freenode) and Valorie Zimmerman, Kubuntu Council (valorie on freenode) 0x458C2FA4.asc Description: application/pgp-keys -- Ubuntu-release mailing list Ubuntu-release@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-release
Re: Yakkety Yak Beta 1
Hello, > I thought you meant "from the UbuntuStudio side"... But i hear from Ross > you might be meaning that you are looking for a volunteer to manage the > whole Beta release for ALL the flavors. Ross will not have the time for > that this time around, and i _Might_ have the time with capital "M"; it > is hard for me to guarantee it before Tuesday... As a last resort, I'll make sure to be around on Thursday, in case Set can't do it. Set, ping me on IRC or send me an email if it comes to it and I'll be happy to help you out (if you are doing the flavor side of things and need help, or you simply can't make it). -- Simon Quigley tsimo...@ubuntu.com tsimonq2 on freenode, OFTC -- Ubuntu-release mailing list Ubuntu-release@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-release
Re: Yakkety Yak Beta 1
Lubuntu will participate in Beta 1. Thanks! -- Simon Quigley tsimo...@ubuntu.com tsimonq2 on freenode and OFTC -- Ubuntu-release mailing list Ubuntu-release@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-release
Lubuntu Next Images
Hello Release Team, The Lubuntu team is ready to begin the migration process to LXQt, and one of the first parts of the migration is getting an image to move to. We have prepared the lubuntu-qt-desktop metapackage and we are ready for an image. A few weeks ago, I submitted two merge proposals[1,2] thanks to advice given by Adam Conrad on #ubuntu-release. On several occasions (on IRC), both myself and Walter Lapchynski have asked for feedback on the merge proposals in an effort to get the images spun up so we can take our next step, but have not received any. This is a call for feedback on those two merge proposals so we can get the images spun up and take our next step. [1] https://code.launchpad.net/~tsimonq2/ubuntu-cdimage/lubuntu-next-image/+merge/301203 [2] https://code.launchpad.net/~tsimonq2/livecd-rootfs/lubuntu-next-image/+merge/301202 Please let us know, Simon Quigley for the Lubuntu team -- Ubuntu-release mailing list Ubuntu-release@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-release
Re: Trusty 14.04.5 Point Release RCs (take two)
Sorry, apologies, meant to send to the Lubuntu lists. :) -- Simon Quigley tsimo...@ubuntu.com tsimonq2 on freenode -- Ubuntu-release mailing list Ubuntu-release@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-release
Re: Trusty 14.04.5 Point Release RCs (take two)
The following affects Lubuntu as well, so we need more testing. On 08/03/2016 10:23 AM, Adam Conrad wrote: > On Tue, Aug 02, 2016 at 06:47:11AM +, Adam Conrad wrote: >> As of now, all flavours should have built or are building RC images >> for the last trusty point release. Please hop on testing them ASAP >> and report feedback on any showstopper bugs. > > Due to a fairly critical bug in X, we're respinning all the 14.04.5 > ISOs right now. I took the opportunity to also slip in a grub2 fix > in the same respin, but otherwise, they should be nearly identical > to the previous images. > > Please test ASAP, as we'd like to release on schedule Thursday. > > ... Adam > -- Simon Quigley tsimo...@ubuntu.com tsimonq2 on freenode -- Ubuntu-release mailing list Ubuntu-release@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-release
Yakkety Yak Alpha 2 Released
"My clarinet sounded like an apoplectic yak. For the brief days I blew the trumpet, a hostile-sounding pig snorted along in jerky fits and starts with the rest of the irritated band." ― Karen Marie Moning The second alpha of the Yakkety Yak (to become 16.10) has now been released! This milestone features images for Lubuntu, Ubuntu MATE and Ubuntu Kylin. Pre-releases of the Yakkety Yak are *not* encouraged for anyone needing a stable system or anyone who is not comfortable running into occasional, even frequent breakage. They are, however, recommended for Ubuntu flavor developers and those who want to help in testing, reporting and fixing bugs as we work towards getting this release ready. Alpha 2 includes a number of software updates that are ready for wider testing. This is still an early set of images, so you should expect some bugs. While these Alpha 2 images have been tested and work, except as noted in the release notes, Ubuntu developers are continuing to improve the Yakkety Yak. In particular, once newer daily images are available, system installation bugs identified in the Alpha 2 installer should be verified against the current daily image before being reported in Launchpad. Using an obsolete image to re-report bugs that have already been fixed wastes your time and the time of developers who are busy trying to make 16.10 the best Ubuntu release yet. Always ensure your system is up to date before reporting bugs. Lubuntu: Lubuntu is a flavor of Ubuntu based on LXDE and focused on providing a very lightweight distribution. The Lubuntu 16.10 Alpha 2 images can be downloaded from: * http://cdimage.ubuntu.com/lubuntu/releases/yakkety/alpha-2/ More information about Lubuntu 16.10 Alpha 2 can be found here: * https://wiki.ubuntu.com/YakketyYak/Alpha2/Lubuntu Ubuntu MATE: Ubuntu MATE is a flavor of Ubuntu featuring the MATE desktop environment for people who just want to get stuff done. The Ubuntu MATE 16.10 Alpha 2 images can be downloaded from: * http://cdimage.ubuntu.com/ubuntu-mate/releases/yakkety/alpha-2/ More information about Ubuntu MATE 16.10 Alpha 2 can be found here: * https://wiki.ubuntu.com/YakketyYak/Alpha2/UbuntuMATE Ubuntu Kylin: Ubuntu Kylin is a flavor of Ubuntu that is more suitable for Chinese users. The Ubuntu Kylin 16.10 Alpha 2 images can be downloaded from: * http://cdimage.ubuntu.com/ubuntukylin/releases/yakkety/alpha-2/ More information about Ubuntu Kylin 16.10 Alpha 2 can be found here: * https://wiki.ubuntu.com/YakketyYak/Alpha2/UbuntuKylin If you're interested in following the changes as we further develop the Yakkety Yak, we suggest that you subscribe to the ubuntu-devel-announce list. This is a low-traffic list (a few posts a week or less) carrying announcements of approved specifications, policy changes, alpha releases and other interesting events. * http://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce A big thank you to the developers and testers for their efforts to pull together this Alpha release! On behalf of the Ubuntu Release Team, Simon Quigley -- Ubuntu-release mailing list Ubuntu-release@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-release
Re: Yakkety Yak Alpha 2
Whoops, forgot about the fact that Ubuntu Studio is out. What about everyone else? -- Simon Quigley tsimo...@ubuntu.com tsimonq2 on Freenode -- Ubuntu-release mailing list Ubuntu-release@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-release
Yakkety Yak Alpha 2
Greetings, Sorry for the late email, but who plans on participating in the Alpha 2 milestone? Lubuntu and Ubuntu MATE (from the message about Alpha 1 Martin stated MATE is participating) are in, Xubuntu is out, and Kubuntu seems to be out from what I've seen on #ubuntu-release. Tim, you said Ubuntu GNOME might participate depending on landings, how's that going? What about the rest of the flavors? -- Simon Quigley tsimo...@ubuntu.com tsimonq2 on Freenode -- Ubuntu-release mailing list Ubuntu-release@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-release
Re: Yakkety Yak Alpha 1 Milestone Release?
It looks like it is still a 4.4 kernel. -- Simon Quigley tsimo...@ubuntu.com tsimonq2 on Freenode -- Ubuntu-release mailing list Ubuntu-release@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-release
Yakkety Yak Alpha 1 Milestone Release?
Greetings, So far from what I have seen, Lubuntu and Ubuntu MATE are the only flavors interested in releasing an Alpha 1 image. Do any other flavors plan on joining in? -- Simon Quigley tsimo...@ubuntu.com tsimonq2 on Freenode -- Ubuntu-release mailing list Ubuntu-release@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-release
Re: Call for Participants for Xenial Alpha 1
Have a nice day, Simon Quigley tsimonq2 Contact for the Ubuntu US Wisconsin LoCo Team Lubuntu Contributor signature.asc Description: This is a digitally signed message part -- Ubuntu-release mailing list Ubuntu-release@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-release
