Tribe 1 freeze ahead
Hello Ubuntu developers, the community is craving for new Linux for Primate Beings, so we will give them the first testing milestone of Gutsy Gibbon, called Tribe 1 on next Thursday [1]. We are about to freeze main by Tuesday. Please get in touch with a member of the release team if you have changes you need to get into this milestone and which are not in the archive already. In particular, if you have important outstanding merges to do, please do them now. Please also help reducing package inconsistencies, as listed on https://wiki.ubuntu.com/PackageInconsistencies. https://launchpad.net/ubuntu/+milestone/tribe-1 is the list of bugs which are targeted to be fixed for Tribe 1. Since this milestone was just created in Launchpad, it is empty right now. Please feel encouraged to milestone show-stopper bugs if you think that they are essential to get fixed for the Tribe release; if in doubt, please err on the safe side and set the milestone, so that the release team can review it. Please also look from time to time to see if there are any bugs there which could use your help. Thanks, Martin Pitt on behalf of the Ubuntu release team [1] https://wiki.ubuntu.com/GutsyReleaseSchedule -- Martin Pitthttp://www.piware.de Ubuntu Developer http://www.ubuntu.com Debian Developer http://www.debian.org signature.asc Description: Digital signature -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
Main frozen for Tribe 1
Hello developers, main has just been frozen for stabilizing Tribe 1. All uploads to main must be approved by me or another member of the release team, so if you have anything urgent which is needed for Tribe 1, please do get in touch ASAP. Uploads to universe will go through as normal (subject to a manual shove, but they will not require review). ETA for the Tribe release is Thursday. Martin -- Martin Pitthttp://www.piware.de Ubuntu Developer http://www.ubuntu.com Debian Developer http://www.debian.org signature.asc Description: Digital signature -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
Main frozen for Tribe-2
Hello developers, main has just been frozen for stabilizing Tribe 2. All uploads to main must be approved by me (pitti on IRC) or Sarah Hobbs (Hobbsee on IRC), so if you have anything urgent which is needed for the Tribe release, please do get in touch ASAP. Please focus on the bugs marked for this milestone: https://bugs.launchpad.net/ubuntu/+bugs?field.milestone:Alist=469 Uploads to universe will go through as normal (subject to a manual shove, but they will not require review). ETA for the Tribe release is Thursday. Martin -- Martin Pitthttp://www.piware.de Ubuntu Developer http://www.ubuntu.com Debian Developer http://www.debian.org signature.asc Description: Digital signature -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
Main frozen for Tribe-4
Hello Ubuntu developers, main has just been frozen for stabilizing Tribe 4. All uploads to main must be approved by me (pitti on IRC), so if you have anything urgent which is needed for the Tribe release, please do get in touch ASAP. Please focus on the bugs marked for this milestone: https://launchpad.net/ubuntu/+bugs?field.milestone:Alist=471 Uploads to universe will go through as normal (subject to a manual shove, but they will not require review). ETA for the Tribe release is Thursday. Thank you, Martin -- Martin Pitthttp://www.piware.de Ubuntu Developer http://www.ubuntu.com Debian Developer http://www.debian.org signature.asc Description: Digital signature -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
Simplified and documented freeze structure
Hello Ubuntu developers, In the past years we accumulated quite a lot of different types of freezes. As recently seen on the mailing list and often on IRC, the multitude of freezes can often be overwhelming and confusing, so after discussing this on ubuntu-devel@ those were cleaned up, consolidated, and properly documented. This is the main entry point: https://wiki.ubuntu.com/UbuntuDevelopment#head-93c8a38bbc124f5d34af970893deffc4bc91700e which lists all kinds of freezes, with links to pages which document each of the freezes in detail. In particular, the following things changed: * StringFreeze and ArtworkDeadline are subsumed under UserInterfaceFreeze now. * UpstreamVersionFreeze was dropped completely. The main things we care about with new upstream versions are: (1) introducing new features, and (2) changing ABI/API, so that we need to do transitions. (1) has always been covered by the already existing FeatureFreeze. The definition of FF has now been updated to cover (2), too. That way, we do not need to make a big fuss about upstream microreleases which only fix bugs and treat upstream bugfix-only microreleases the same way as we treat new syncs/merges from Debian. We already do that in practice for e.g. system-config-printer, where we have brilliant upstream connections, and fixes immediately go upstream. We believe this makes sense because for the purposes of release management it is not really important whether fixes come directly from upstream or from Debian or us. The ABI/API break would then be mentioned in the description of FeatureFreeze. * NewPackagesFreezeUniverse is subsumed by FF now, too, since they are just features on the distro level. Originally, this freeze was scheduled a bit later than FF in gutsy. However, since reviewing new source packages takes some days up to a few weeks, it has never been clear when to do the cut. The new definition of FF clearly defines this process now. * DocumentationStringFreeze has been added to the official freeze list. It has existed for a long time already, and is a freeze for the documentation team, not for the packages in the distribution. However, since it is important for the entire process, it should be listed on the page, too. According to those changes, the instructions how to request exceptions [1] have been updated for above changes. The other pages which refer to those freezes have been updated as well ([2], [3]). Thank you for your attention, Martin Pitt on behalf of the Ubuntu Release Team. [1] https://wiki.ubuntu.com/FreezeExceptionProcess [2] https://wiki.ubuntu.com/GutsyReleaseSchedule [3] https://wiki.ubuntu.com/ReleaseScheduleTemplate -- Martin Pitthttp://www.piware.de Ubuntu Developer http://www.ubuntu.com Debian Developer http://www.debian.org signature.asc Description: Digital signature -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
Intrepid Ibex Alpha-4 released
Intrepid Ibex Alpha-4 released Hello Ubuntu developers, Welcome to Intrepid Ibex Alpha-4, which will in time become Ubuntu 8.10. Pre-releases of Intrepid 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 developers and those who want to help in testing, reporting, and fixing bugs. Alpha 4 is the fourth in a series of milestone CD images that will be released throughout the Intrepid development cycle. The Alpha images are known to be reasonably free of showstopper CD build or installer bugs, while representing a very recent snapshot of Intrepid. You can download it here: http://cdimage.ubuntu.com/releases/intrepid/alpha-4/ (Ubuntu) http://cdimage.ubuntu.com/edubuntu/releases/intrepid/alpha-4/ (Ubuntu Education Edition) http://cdimage.ubuntu.com/kubuntu/releases/intrepid/alpha-4/ (Kubuntu) http://cdimage.ubuntu.com/xubuntu/releases/intrepid/alpha-4/ (Xubuntu) See http://wiki.ubuntu.com/Mirrors for a list of mirrors. Alpha 4 includes a number of software updates that are ready for large-scale testing. Please refer to http://www.ubuntu.com/testing/intrepid/alpha4 for information on changes in Ubuntu. This is quite an early set of images, so you should expect some bugs. For a list of known bugs (that you don't need to report if you encounter), please see: http://www.ubuntu.com/testing/intrepid/alpha4 If you're interested in following the changes as we further develop Intrepid, have a look at the intrepid-changes mailing list: http://lists.ubuntu.com/mailman/listinfo/intrepid-changes We also suggest that you subscribe to the ubuntu-devel-announce list if you're interested in following Ubuntu development. 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 Bug reports should go to the Ubuntu bug tracker: https://bugs.launchpad.net/ubuntu Enjoy, -- Martin Pitt On behalf of the Ubuntu release team signature.asc Description: Digital signature -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
Main frozen for Alpha-1
Hi all, We're about two days before the expected release of Karmic Alpha 1, so the milestone freeze is now in effect. Please take care that any packages that you upload to main between now and the Alpha 1 release will help us in the goal of a high quality and timely alpha, and hold any disruptive or unnecessary uploads until after the alpha is out. The list of blocking bugs for alpha-1 is currently empty, but during image testing it is expected to get some: https://bugs.launchpad.net/ubuntu/jaunty/+bugs?field.milestone=2209 Last night's updates caused a lot of breakage unfortunately, despite the early warning last Friday. There's plenty of other work to be done in getting the archive in a consistent state so that we don't have uninstallable packages for the alpha-1 milestone: https://wiki.ubuntu.com/UbuntuDevelopment/PackageArchive#Consistency Remember that this is a soft freeze, so you are each responsible for making sure your uploads are appropriate - Launchpad will not be your safety net. Packages that are not seeded on the CDs (i.e., most packages in universe, with the exception of UbuntuStudio, Xubuntu, and Mythbuntu packages) may be uploaded as usual. Thanks for your cooperation, Martin Pitt on behalf of the Ubuntu release team -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) signature.asc Description: Digital signature -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
Re: Main frozen for Alpha-1
Martin Pitt [2009-05-12 8:52 +0200]: The list of blocking bugs for alpha-1 is currently empty, but during image testing it is expected to get some: https://bugs.launchpad.net/ubuntu/jaunty/+bugs?field.milestone=2209 Sorry, that should be: https://bugs.launchpad.net/ubuntu/karmic/+bugs?field.milestone=12709 Martin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) signature.asc Description: Digital signature -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
Karmic Alpha 1 released
People often call me a bear, While up in the tree I haven’t a care, Eating the leaves of the Eucalyptus tree, All the while feeling so free, When born, but the size of a hummingbird. -- Nate Robert Groschen Welcome to Karmic Koala Alpha 1, which will in time become Ubuntu 9.10. Pre-releases of Karmic 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 developers and those who want to help in testing, reporting, and fixing bugs. Alpha 1 is the first in a series of milestone CD images that will be released throughout the Karmic development cycle. The Alpha images are known to be reasonably free of showstopper CD build or installer bugs, while representing a very recent snapshot of Karmic. You can download it here: http://cdimage.ubuntu.com/releases/karmic/alpha-1/ (Ubuntu) http://cdimage.ubuntu.com/kubuntu/releases/karmic/alpha-1/ (Kubuntu) http://cdimage.ubuntu.com/xubuntu/releases/karmic/alpha-1/ (Xubuntu) See http://wiki.ubuntu.com/Mirrors for a list of mirrors. The primary changes from Jaunty have been the re-merging of changes from Debian, updating to the current Linux kernel, and updating GNOME to the current development release. There are also some infrastructure changes for power management and the Intel video driver. Please see the technical notes for details: http://www.ubuntu.com/testing/karmic/alpha1 Please note that the desktop CD isn't ready yet. This release consists only of the alternate and server CDs; the desktop CD will follow in the next Alpha release. If you're interested in following the changes as we further develop Karmic, have a look at the karmic-changes mailing list: http://lists.ubuntu.com/mailman/listinfo/karmic-changes We also suggest that you subscribe to the ubuntu-devel-announce list if you're interested in following Ubuntu development. 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 Bug reports should be reported as described on https://help.ubuntu.com/community/ReportingBugs Enjoy, Martin Pitt On behalf of the Ubuntu release team signature.asc Description: Digital signature -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
Apport now supports interactive package hooks
Hello fellow developers, So far, Apport package hooks were limited to collecting data from the local system. However, a lot of debugging recipes and standard bug triage ping pong involves asking the reporter further questions which need reponses from a human. This can range from a very simple information message box “Now, please plug in the camera which is not detected” until a complex decision tree based on the symptoms the user sees. As discussed at UDS Barcelona [1], Apport now supports this, as of version 1.3 (just uploaded to Karmic). The GUI still leaves something to be desired, and I plan to improve it. But the API for hooks won’t change any more, so you can now begin to develop your interactive hooks. Please see my blog [2] for how such an interactive hook might look like, and [3] or [4] for the documentation. I also updated https://wiki.ubuntu.com/Apport/DeveloperHowTo accordingly. Enjoy, and don't hesitate to contact me for assistance, help, and suggestions for improvements! Thanks, Martin [1] https://wiki.ubuntu.com/DesktopTeam/Specs/Karmic/SymptomBasedBugReporting [2] http://martinpitt.wordpress.com/2009/06/08/interrogation-with-apport-hooks-qt-developer-needed/ [3] /usr/share/doc/apport/package-hooks.txt [4] http://bazaar.launchpad.net/~apport-hackers/apport/trunk/annotate/head%3A/doc/package-hooks.txt -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) signature.asc Description: Digital signature -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
Next karmic gdm upgrade WILL BREAK your system
Hello Karmic users, last Wednesday the new gdm 2.26 landed in Karmic and has caused quite a bunch of regressions and errors. I just uploaded 2.26.1-0ubuntu3 which should fix the nasty ones, the only major one left is the Does not support session saving dialog (https://launchpad.net/bugs/395324), which I'm going to address next. One major bug in the first 2.26 packages was that the package scripts restarted gdm during the upgrade (https://launchpad.net/bugs/395302). The package scripts got fixed in 2.26.1-0ubuntu3, so that _from this version on_ further upgrades will go smoothly. Upgrades from 2.20 (i. e. Jaunty or Karmic Alpha 2) will also work. But if you upgraded to gdm 2.26 since last Friday, updating your system under GNOME will kill the upgrade and your session in the middle of the update again, since there is no way for the fixed gdm version to override the previous version's prerm script. Please follow these steps: 1. Check your gdm version: dpkg -l gdm If this says 2.20..., you are fine and can ignore this email. 2. Do sudo apt-get update apt-cache show gdm|grep Version:|head -n 1 If the second command says 2.26.1-0ubuntu3, continue; otherwise, wait for an hour. The version should be available on archive.ubuntu.com at 1600 UTC today, and a bit later on your mirror. 3. Log out from your X session, to get back to the login manager. 4. Press Control-Alt-F1 to get to a text console, and log in with your normal username/password. 5. Run an upgrade: sudo apt-get dist-upgrade 6. Press Ctrl+Alt+F7 to get back to the graphical login manager. Thank you and sorry for the inconvenience, Martin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) signature.asc Description: Digital signature -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
Minutes from the Technical Board meeting, 2009-10-06
Copied from https://wiki.ubuntu.com/TechnicalBoard/TeamReports/09/October: = Attendees = Martin Pitt (chair) Mark Shuttleworth Matt Zimmerman Scott James Remnant Colin Watson = Notes = * Review actions from last meeting * ''Keybuk to find Bdale at LinuxCon to hash out participation'': done; Bdale will watch a few meetings, then have a discussion. He is on the TB mailing list now. * ''kees to drive sun-java6 email thread and get resolution on responsibility'': Neil is soliciting migration plans; needs to be discussed in-depth at next UDS; Colin made a note about handling it in the foundations track * ''cjwatson to drive DMB email thread to conclusion'': followup happened, voting is ongoing * ''Keybuk to finalize unit policy and email to TB for vote'': deferred * ''cjwatson to drive vote on Archive Reorg rights for ubuntu-desktop and mythbuntu in email'': Blocked on DMB email thread conclusion, deferred * Archive reorganization: * There is a [[https://launchpad.net/~kubuntu-dev]] team now which has been blessed by the Kubuntu council; Colin will follow up * Naming of new packages: * mdz raised the problem that newly created projects often change their name shortly after they get introduced to the wide audience (example: software-store → software-center, espresso → ubiquity); is there a possible process enhancement for this? * Keybuk: renaming packages later is better than introducing packages later (and getting fewer feedback) * pitti: does not happen often enough to be a major concern * cjwatson: we don't need to do this for packages that aren't really significantly user-visible * mdz will come back with a list of packages which were renamed and how much developer effort was wasted, to see whether any followup is required * core-dev application process * TB → DMB application handling is currently in flux, and there were objections against the proposed process * DMB meeting next Tuesday 1400 UTC to settle on a process * Select a chair for the next meeting * Keybuk * Actions from this meeting: * Keybuk to finalize unit policy and email to TB for vote * cjwatson to drive vote on Archive Reorg rights for ubuntu-desktop and mythbuntu in email * pitti to announce DMB meeting next Tuesday 1400 -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) signature.asc Description: Digital signature -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
Developer Membership Board public meeting about approval process
Hello Ubuntu community, We recently shifted the responsibility for approving new Ubuntu developres from the Technical Board (TB) to the new Developer Membership Board (DMB). This, and the parallel ongoing archive/privilege restructuring raised some disputes how the future process of developer approval should look like. There will be a DMB meeting next week at Tuesday, October 13th, at 14:00 UTC in #ubuntu-meeting. It is a public meeting, so everyone is welcome to attend. Martin Pitt cf. Ubuntu Technical Board -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) signature.asc Description: Digital signature -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
Debian and Ubuntu now use the same patch tagging guidelines
Hello Ubuntu developers, We have long had a policy for adding standard meta information to patches that we apply to Ubuntu, to make it easier to track their origin, upstream status, etc. Debian now introduced a new policy proposal which has the same spirit, but a slightly different format (mainly to stay compatible with git-formatted patches): http://dep.debian.net/deps/dep3/ After a discussion on ubuntu-devel[1], it now turns out that the Debian proposal is stable enough to become widely adopted. Thus our own policy for this [2] now by and large is just a pointer to DEP-3. So it would be nice if from now on we could migrate to that new format over time. This is of course neither urgent, nor bound to a particular release. Thanks all, Martin [1] https://lists.ubuntu.com/archives/ubuntu-devel/2009-September/029212.html [2] https://wiki.ubuntu.com/UbuntuDevelopment/PatchTaggingGuidelines -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) signature.asc Description: Digital signature -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
Developer Membership Board public meeting: 2009-11-24 15:00 UTC
Hello Ubuntu community, We have a fair backlog of main upload requests. We will hold a DMB meeting next week at Tuesday 15:00 UTC in #ubuntu-meeting to process those. Everyone is welcome to attend. If you have a pending application to main upload privileges, it would be appreciated if you could participate. Thank you, Martin p. p. the Developer Membership Board -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) signature.asc Description: Digital signature -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
Minutes from the Technical Board meeting, 2009-11-17
Technical Board meeting, 2009-11-17 = Attendees = * Martin Pitt (chair) * Mark Shuttleworth * Kees Cook * Colin Watson * Scott James Remnant = Topics = * Archive reorganization: * Upload delegation for ubuntu-desktop: Approved * [ACTION]: Martin to talk to Jonathan about making DMB an admin of kubuntu-dev (done now), and to announce new members to devel-permissions@ and kubuntu team list * [ACTION] Martin to talk to Mario about adding DMB as admin of ~mythbuntu-dev and add wiki page about new member procedure * Upload delegation for ubuntu-desktop: Approved * Upload delegation for kubuntu-dev: Approved pending fixes from above * Upload delegation for mythbubuntu-dev: Approved pending fixes from above * [ACTION] Colin to document edit_acl invocation for setting team upload delegation * [ACTION] Colin to implement delegations for these three teams after above fixes * Units Policy: * [ACTION] Scott to redraft Units policy to address Scott's and Matt's concerns and clean up language * Change of Ubuntu Translations permission policy: approved; Martin changed the permissions on Launchpad and asked David Planella to announce to -translat...@. * 10.04 LTS release plan: * updated wiki page to point out that different products might have different LTS states * LTS status for Kubuntu 10.04 is currently being discussed at UDS * In the future we will clearly announce which products have which LTS status at the beginning of the cycle, so that developers and customers can plan better * Ubuntu Licensing Policy: * [ACTION] Colin to clarify trademark/license distinction on licensing policy * Execute Permission Policy: * The current policy will not handle all potential cases, such as OO.o macros or application cases which wer are unaware of * Colin: we should point out an alternative approach instead of just saying No * current impact: kill GNOME desktop do you want to run it anyway? question, remove a few MIME handlers * To be continued in the next meeting * https://wiki.kubuntu.org/Kubuntu/UpdatesPolicy: deferred, out of time * DMB items: deferred, out of time; [ACTION] Martin to announce DMB meeting next week * Check on community bugs: None * Chair for next meeting: Kees -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) signature.asc Description: Digital signature -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
Unified SRU policy and team for main/universe
Hello Ubuntu developers, during the course of general archive reorganization, and a recent (short) discussion on ubuntu-devel@ [1] and on IRC, the SRU teams for main (ubuntu-sru) and universe (motu-sru) have now joined together in https://launchpad.net/~ubuntu-sru This now means that any member can review/approve/reject any SRU request. (However, only the archive administrators amongst the team members can actually press the buttons to accept uploads, but that's the smallest part of SRU review really). The policy was already updated a while ago to uniquely apply to the entire archive: https://wiki.ubuntu.com/StableReleaseUpdates In particular, you now should just subscribe ubuntu-sru to all SRU requests. motu-sru will still work, since ubuntu-sru is now the sole member of motu-sru, but its usage should be phased out. Thank you for your attention, Martin [1] https://lists.ubuntu.com/archives/ubuntu-devel/2009-December/029640.html -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) signature.asc Description: Digital signature -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
Minutes from the Technical Board meeting, 2010-05-04
Technical Board meeting, 2010-05-04 === This is also available online at: https://wiki.ubuntu.com/TechnicalBoard/TeamReports/10/May Attendees: Martin Pitt (chair), Kees Cook, Matt Zimmerman, Colin Watson, Mark Shuttleworth Guests: Jonathan Riddell, Scott Kitterman, Emmet Hikory == Action review == * Riddell and ScottK to sort next steps of KDE Updates process * Outstanding, but there was progress this week * cjwatson to write up 2010-03-09 meeting minutes * Outstanding * cjwatson to drive libfaac issue to conclusion * Outstanding == Scan the mailing list archive for anything we missed == * That was done, added to agenda below == Request for Kubuntu Unseeded Packages Team == * Would be best to create an explicit list of packages as a seed, based on the reverse dependency criterion * Once this list is done, DMB can implement == Scope of Canonical's acquired ffmpeg patent licenses for derivatives == * This is believed to be strictly an OEM business, and not apply to Ubuntu in general * [ACTION] Martin to confirm with Canonical's legal department and follow up == Default sync source for Maverick == * During lucid we synced from Debian testing by default; recently a survey[1] was done (summary at [2]) * The TB unanimously voted for switching back to unstable for Maverick * [ACTION] cjwatson to switch MoM * [ACTION] pitti to get Soyuz' sync-source.py switched Chair for next meeting: Mark Shuttleworth Martin Pitt p.p. Ubuntu Technical Board [1] https://lists.ubuntu.com/archives/ubuntu-devel/2010-April/030594.html| [2] https://lists.ubuntu.com/archives/ubuntu-devel/2010-April/030655.html -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) signature.asc Description: Digital signature -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
Mass build failure in Maverick today
Hello Ubuntu developers, I uploaded a new version of pkgbinarymangler this morning, which had an unintended side effect that caused apt/dpkg to fail to install all packages. The consequence of this was that all maverick builds for Ubuntu as well as PPAs which were done between 09:00 and 12:00 UTC today failed to build. pkgbinarymangler has been fixed now, and I retried all affected maverick builds for Ubuntu, so for those you do not need to perform any action, except removing and ignoring the FTBFS emails that you got. However, I cannot retry the builds for PPAs. If you got an FTBFS log which has a lot of lines like dpkg: error processing /var/cache/apt/archives/python2.7-dev_2.7-2~ppa1_i386.deb (--unpack): corrupted filesystem tarfile - corrupted package archive then please retry the build on Launchpad, it will succeed now. I am terribly sorry for the hassle, thanks for your understanding. Martin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) signature.asc Description: Digital signature -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
Minutes of the Technical Board meeting 2010-09-21
This is also available on the wiki: https://wiki.ubuntu.com/TechnicalBoard/TeamReports/10/September Chair: Martin Attendees: Colin Watson, Kees Cook, Scott James Remnant Guests: Jamie Strandboge * Review of Actions * Martin to follow up with Kees on-list (re: Chromium security updates) -- '''DONE''' * Matt to implement brainstorm reviews as proposed -- '''DONE''' * Martin added this as a permanent topic to the agenda, together with the next due date * Matt to respond to jono re: application review board -- '''DONE''' * SRU microrelease exception for bzr (https://lists.ubuntu.com/archives/technical-board/2010-September/000506.html): * Requirement: Run selftests during package build to catch architecture specific regressions, and catch problems early * Run tests on installed package as part of SRU verification * '''ACTION:''' Martin Pitt to ask Martin Pool about self test instructions on installed system * '''ACTION:''' Kees to add bzr self test to qa-regression-testing project * Under those conditions, the request was unanimously approved * '''ACTION:''' Martin add to StableReleasePolicy * Chromium security updates * Discussion has shown that a general SRU exception is the only viable way * It is not realistic to do any serious testing on these, since updates are released so fast; updates need t o happen pretty much blindly * It is not realistic to do any serious testing on these, since updates are released so fast * This makes it rather inappropriate for main/default install, but as an opt-in in universe the current experience with the recent Chromium SRUs showed that the process is working * In case of new build dependencies: in general they should be bundled, but for some of them it is okay to update the system package (e. g. gyp, and perhaps libvpx); this is a case-by-case decision * No new community bugs to look at * Next chair: Mark Shuttleworth Martin Pitt p.p. Ubuntu Technical Board -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) signature.asc Description: Digital signature -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
Default umask in oneiric is now 002
Hello fellow developers, with today's pam upload, the default umask for users whose primary group is a private user group (like group martin for user martin) is now automatically changed from the 022 default to 002. This means that files are now created as being group-writable. This does not really change any effective permissions in default setups, but makes it easier to share files between trusted user accounts, i. e. if you put your spouse, kids, etc. into your private user group. Please let me know if this causes any unexpected regression or trouble. https://blueprints.launchpad.net/ubuntu/+spec/umask-to-0002 is the associated blueprint. Thanks, Martin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) signature.asc Description: Digital signature -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
New SRU team member: Chris Halse Rogers
Hello Ubuntu developers, I'm happy to announce that Chris Halse Rogers (RAOF on IRC) stepped up to join the ranks of the SRU team. So from now on we have three persons (Chris, Clint Byrum, and me) who will share the load, and you are going to see SRU reviews in the bugs from him as well. So please feel free to ping him about SRU matters as well. This means that we now have all timezones 24 hour coverage for SRUs, with Chris being in Australia, Clint in the US, and me in Europe. Note that Chris is not an archive admin yet, so I will still press the buttons to accept the uploads, but after some weeks he certainly will be able to do so himself. Thanks Chris! Martin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) signature.asc Description: Digital signature -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
Minutes of the Technical Board meeting, 2011-06-30
Also available on the wiki at https://wiki.ubuntu.com/TechnicalBoard/TeamReports/11/June Chair: Martin Pitt Present: Mark Shuttleworth, Colin Watson, Kees Cook * Setting the Ubuntu series release manager in Launchpad to ubuntu-release * No further problems with this expected, Colin agreed to doing the switch * Things to check: * non-release-team core-devs can target tasks to oneiric; already tested in https://bugs.launchpad.net/launchpad/+bug/451390/comments/10 * non-core-dev release team members can modify oneiric milestones * Measuring installation success/failure, updated proposal from Evan Dandrea: https://lists.ubuntu.com/archives/technical-board/2011-June/000935.html * the purpose of collecting the data is to make Ubuntu better * while we won't make the data entirely public (avoiding unexpected privacy concerns, and competitive questions), people with technical/research projects who have a need for it can ask the TB for data (this includes Canonical employees) * for opt-out we need to write a privacy policy * people who are concerned about what data we're collecting can of course examine the client source code; we won't correlate IP addresses with this * we need to discuss data security (against theft) with IS * This proposal, under above conditions, got 4 out of 4 votes from the present TB members; for the record, Scott James Remnant mentioned that he'd prefer having all the data being public * SRU microrelease exception for Banshee * Upstream clarified and documented patch backporting and QA policy: https://live.gnome.org/Banshee/StableReleasesPolicy * Got 4 out of 4 votes from the present TB members, accepted; wiki page updated accordingly * DMB voting procedure was discussed quickly, but we ran out of time. Will be discussed via email or carried to next meeting. * Policy proposal for partner repository: Ran out of time, carried to next meeting. -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) signature.asc Description: Digital signature -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
Soft freeze in effect for Oneiric Alpha 2
Hello Ubuntu developers, Two days out from the expected release of Maverick Alpha 3, the milestone freeze is now in effect. Please take care that any packages that you upload to main between now and the Alpha 3 release will help us in the goal of a high quality and timely alpha, and hold any disruptive or unnecessary uploads until after the alpha is out. Again, this means the primary focus should be on resolving these bugs: https://bugs.launchpad.net/ubuntu/oneiric/+bugs?field.milestone%3Alist=39141field.tag=-ftbfs As always, there's also plenty of other work to be done in getting the archive in a consistent state so that we don't have uninstallable packages for the alpha-2 milestone: https://wiki.ubuntu.com/UbuntuDevelopment/PackageArchive#Consistency Remember that this is a soft freeze, so you are each responsible for making sure your uploads are appropriate - Launchpad will not be your safety net. Packages that are not seeded on the CDs (i.e., most packages in universe, with the exception of Ubuntu Studio, Xubuntu, and Mythbuntu packages) may be uploaded as usual. Thank you, Martin Pitt pp. the Ubuntu Release Team -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) signature.asc Description: Digital signature -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
Re: Soft freeze in effect for Oneiric Alpha 2
Martin Pitt [2011-07-05 8:12 +0200]: Two days out from the expected release of Maverick Alpha 3, the milestone freeze is now in effect. Please take care that any packages that you upload to main between now and the Alpha 3 release Sorry about the copypaste error. Of course this was meant to be Oneiric Alpha 2. Martin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) signature.asc Description: Digital signature -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
Technical Board meeting minutes (2011-10-06)
This is also available on the wiki: https://wiki.ubuntu.com/TechnicalBoard/TeamReports/11/October Meeting: 2011-10-06 Chair: Martin Pitt Attendees: Kees Cook, Stephane Graber Guests: Allison Randal, Scott Kitterman, Lamont Jones = Brainstorm review update = Cycle completed, see Colin's summary: http://www.chiark.greenend.org.uk/ucgi/~cjwatson/blosxom/ubuntu/2011-10-06-brainstorm-review.html = Recruiting new members for the ARB (Allison) = Proposal: https://wiki.ubuntu.com/AppReviewBoard/Restaffing This was discussed and edited to add the requirement that new board members must be Ubuntu developers, i. e. ~ubuntu-dev members. This does not retroactively apply to the already existing members, though. Proposal carried with 3 for, 0 against, 0 abstained. = Postfix microrelease exception request (Scott K) = Upstream has tight requirements for what goes into stable microreleases, QAs them with regression tests, and has a good history of not breaking anything. Known breakage so far was in the packaging. Our QA regression testing repository has an [[http://bazaar.launchpad.net/~ubuntu-bugcontrol/qa-regression-testing/master/view/head:/scripts/test-postfix.py|existing integration test script]] which should be run on the proposed packages for checking for general mis-builds, packaging errors, etc. Team members generally feel good about routinely SRUing microreleases, but want to see an existing successful SRU first. Martin signed up for reviewing that SRU. This will be re-discussed after that. Martin Pitt p.p. Ubuntu Technical Board -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) signature.asc Description: Digital signature -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
New Apport feature: Client-side duplicate detection
Hello fellow developers, I just released Apport 1.90 and uploaded it into Precise. This version introduces client-side duplicate checking. So from now, when you report a crash, you are likely to see “We already know about this” right away, without having to upload or type anything, and you will get directed to the bug page. If you get this, please mark yourself as affected and/or subscribe to the bug, both to get a notification when it gets fixed, and also to properly raise the “hotness” of the bug to bubble up to developer attention. Please let me know at once if you see this system acting up and being wrong. This is still a fairly new and not much tested approach, so there might be cases where the new way of duplicate detection goes wrong. This also means that from now on it should not be necessary to write manual bug patterns for crashes. We still need bug patterns for common package installation failure situations, or in general any bug which is not a crash which we can identify from log files, etc. If you are interested in some background and technical details, please see the longer version of this announcemnt [1]. Thanks, Martin [1] http://www.piware.de/2011/11/apport-1-90-client-side-duplicate-checking/ -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) signature.asc Description: Digital signature -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
Minutes of the Technical Board meeting 2013-02-18
Note, this is also available in the wiki: https://wiki.ubuntu.com/TechnicalBoard/TeamReports/13/February Chair: Martin Pitt Attendees: Colin Watson, Stéphane Graber, Soren Hansen Guests: Anthony Wong, Jack Yu Apologies: Matt Zimmerman, Kees Cook = Action review = * Colin to clarify the SRU documentation in light of Steve's comments on bundling: '''done''' = Flavor of Ubuntu Kylin https://wiki.ubuntu.com/UbuntuKylin = * The Technical Board welcomes the Kylin community to take up a real Chinese Ubuntu flavour, as the Ubuntu Developer team has traditionally lacked Chinese specific skills * The individual points of above document have been discussed, and most items regarded as genuine localization. However, there were a few points which were requested to be clarified/changed. * Chinese Input Method: Using fcitx will not be compatible with the Ubuntu/Unity/GNOME assumptions of using ibus, i. e. this will not work with e. g. control-center, the keyboard indicator, and the ibus indicator. * ''ACTION:'' JackWu to document justification for switching to fcitx, and impact on control center, indicators, application support * Cooperation with WPS: The TB feels that promoting proprietary software in the installer and default desktop is against the spirit and letter of the Ubuntu brand and philosophy and should not be done. Easy installation through Software Center is perfectly valid of course. * ''ACTION:'' JackYu to clarify on the wiki page what WPS is, how it's going to be integrated, and status of Libre``Office * System Assistant, Photo Handling: These two are not Chinese specific, but should rather be done in the general Ubuntu context; System Assistant sounds like the old computer-janitor, a potential successor of which should be implemented in software-center proper * ''ACTION:'' JackYu to clarify goals and details for both * The guidelines for accepted Ubuntu flavours require a signed CoC, one or more developers have upload rights, show 6 months activity and have a QA contact * ''ACTION:'' JackYu and Anthony Wong to sign CoC * The TB recognizes that requiring already existing upload rights is not something we can enforce in this case, and that developer merits should be acquired while working on Kylin instead. This should be reviewed in six months, until then the Foundations team has agreed to be formally responsible for the flavour and help out with mentoring, sponsoring, and release engineering. = SRU Minor Release Exception for Ceph = * https://lists.ubuntu.com/archives/technical-board/2013-February/001475.html * Deferred to email as we ran out of time No pending community bug reports. Chair for next meeting: Kees (carried over) Next meeting is on 2013-03-04. -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) signature.asc Description: Digital signature -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
Minutes of Technical Board meeting from 2013-05-13
Also available on the wiki at https://wiki.ubuntu.com/TechnicalBoard/TeamReports/13/May Chair: Martin Pitt Other members in attendance: Stéphane Graber, Soren Hansen Apologies: Matt Zimmerman, Colin Watson Full log: http://ubottu.com/meetingology/logs/ubuntu-meeting/2013/ubuntu-meeting.2013-05-13-20.07.log.html = SRU request for custom unity-greeter indicators (Mike Terry) = * One positive answer on the ML, no objection from other members. Granted. = openssl as a system library (Dave Walker) = * Carried over to next meeting as Colin has a strong and well-founded position but could not make it to today's meeting. = SRU approved without waiting in unapproved (Jonathan Riddell) = * Unanimous agreement that this is not a flaw in the defined SRU process, but a flaw in its execution. We do not want to give up peer review for what goes into stable releases, and rather want to address the workflow problem in the SRU team. * ACTION: Martin to mail SRU team members about this = Brain storm review = * Due to radically decreasing interest from both Ubuntu developers (judging by the decrease of answers) as well as users (judging by the decreasing number of voters) the TB feels that it is time to end brainstorm.ubuntu.com and its regular review. * The sole remaining maintainer (Stephane Graber) as well as the Ubuntu community QA team (who founded this service initially), represented by Jorge Castro and Nicholas Skaggs, all agree. * ACTION: Jorge to check whether brainstorm.ubuntu.com could be kept as a read-only archive, and otherwise shut it down. Chair for next meeting: Kees Cook -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) signature.asc Description: Digital signature -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
Minutes of the Technical Board Meeting 2013-07-22
Wiki link: https://wiki.ubuntu.com/TechnicalBoard/TeamReports/13/July = Meeting 2013-07-22 = * Attendees: Martin Pitt (chair), Kees Cook, Matt Zimmerman, Colin Watson, Soren Hansen, Stéphane Graber * Guests: Rick Spencer, Scott Kitterman, Stefan Bader * Action review: * Kees to review outstanding provisional MREs -- carried over * Development series alias name * We concluded the discussion from the previous meetings (see https://wiki.ubuntu.com/TechnicalBoard/TeamReports/13/June), and after much back and forth discussion between the three candidates rolling, next, and devel, the TB voted for ''devel''. * SRU MRE: Xen * Provisional MRE was granted, with the constraint that some formal testing procedures should be discussed in the first SRU. This could be something like boot the last N releases/LTS default install and verify some list of things (networking, file system test suite, etc.) * SRU: Extend the KDE MRE * Scott proposed an extension of the existing KDE microrelease exception to cover non-core applications: https://lists.ubuntu.com/archives/technical-board/2013-July/001666.html * The list was granted for MRE except lightdm-kde, as regressions there have a potentially disastrous effect. That particular package will be reviewed once there is an actual new microrelease to consider. Martin Pitt p. p. the Ubuntu Technical Board -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) signature.asc Description: Digital signature -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
autopkgtesting now running on armhf and ppc64el -- apologies for spamming
Hello Ubuntu developers, this week Jean-Baptiste and I worked on enabling autopkgtests on armhf and ppc64el. They will soon appear on https://jenkins.qa.ubuntu.com/view/Trusty/view/AutoPkgTest/ as separate views (AutoPkgtest armhf and AutoPkgtest ppc64el). Until that has been configured, Canonical folks can see them on http://d-jenkins.ubuntu-ci:8080/view/Trusty/view/AutoPkgTest/ We now did a mass run of all available tests on both architectures. Unfortunately we forgot to disable email notifications for that, so you will be getting a lot of failures (for all the packages where you were the last uploader). I'm really sorry about that, please just ignore them. There are currently a lot of failures, for various reasons. Some tests might not work on ARM/ppc64el, might have insufficient dependencies, or can't run in a container and need a full VM instead. Until we fix britney to ignore tests that never succeeded on a particular architecture we will thus NOT use these test results for gating propagation from -proposed to release. Thank you, and apologies again for the mail spam, Martin Pitt -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) signature.asc Description: Digital signature -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
Recent improvements in autopkgtest, change of CI infrastructure next cycle
or have a suggestion for a small improvement, please file a bug against autopkgtest. If you want to help out with autopkgtest development or the services around it (like http://ci.debian.net), or want to discuss bigger new features, please do that on the mailing list [4]. Thanks for your attention! Martin Pitt [1] http://dep.debian.net/deps/dep8/ [2] http://metadata.ftp-master.debian.org/changelogs/main/a/autopkgtest/unstable_changelog [3] http://anonscm.debian.org/gitweb/?p=autopkgtest/autopkgtest.git;a=blob_plain;f=doc/README.running-tests [4] http://lists.alioth.debian.org/mailman/listinfo/autopkgtest-devel -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) signature.asc Description: Digital signature -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
Cloud images and ubuntu package testing now use systemd
Hello all, this morning I discovered that our daily cloud images got switched to booting with systemd last night. I adjusted the daily autopkgtest CI image build process to cope with that, and it looks good again. That means that all package tests in Ubuntu CI, i. e. on https://jenkins.qa.ubuntu.com/view/Vivid/view/AutoPkgTest/ are running under systemd now. This apparently caused some regressions in e. g. https://jenkins.qa.ubuntu.com/job/vivid-adt-heat/? and maybe a few others, so if you look at why your package started failing its tests, this is a very likely reason. For those who wonder, we still plan to switch vivid to systemd by default, but the FFE [1] is still pending. I'll send a warning/instructions announcement before that happens. Thanks, Martin [1] https://launchpad.net/bugs/1427654 -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) signature.asc Description: Digital signature -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
Announce: Vivid will switch to booting with systemd next Monday, brace for impact
Hello all, it should be no secret any more, but it'll get serious now: we will switch Ubuntu Vivid to boot with systemd instead of upstart. That is, desktop, server, cloud/autopkgtests (that already happened two days ago), and all flavors. snappy has used systemd from day one. We will *not* switch Ubuntu Touch, however [1]. As per the feature freeze exception [2] this is scheduled to happen on Monday. Technically, this will flip around the preferred dependency of init to systemd-sysv | upstart, which will affect new installs, but not upgrades. Upgrades will be switched by adding systemd-sysv to ubuntu-standard's dependencies. So if you already want to do this change today, you can switch today already if you want. If you never booted your system with systemd before, it's advisable to do an one-time boot first. Please see https://wiki.ubuntu.com/SystemdForUpstartUsers#Switching_init_systems for details. This also explains how to move back to upstart for one boot or permanently. If you run into any trouble, please do file a bug (ubuntu-bug systemd)! I'll do my best to keep up with them. Please have a look at /usr/share/doc/systemd/README.Debian for some debugging tips. Contingency plan: If after some weeks we find that there are too many or too big regressions, we can revert to upstart by default with two simple uploads (ubuntu-standard and init). Thanks, Martin [1] This is blocked on most platforms currently running an ancient 3.4 kernel. Also, there's some porting work to do on the upstart jobs, but that's low priority due to the former. [2] https://bugs.launchpad.net/bugs/1427654 -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) signature.asc Description: Digital signature -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
proposed-migration autopkgtest now switched to new cloud infrastructure
Hello again, The new cloud-based autopkgtest infrastructure that got announced in [1] has run for three weeks and is working reasonably reliable now (which is: already way more reliable than the old Jenkins based machinery). Thus it is time to flip the switch, and I just rolled out proposed-migration (aka britney) to only trigger and evaluate autopkgtests from the cloud setup. Thus http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html is now back to only showing one set of tests again, the (informational) bits are gone and are now the primary data. Some things to be aware of == - Regression is now determined on a per-architecture level, i. e. if a package never succeeded on i386 but did succeed on amd64, the former will count as always failed (and thus not block promotion), the latter as regression. - No more Jenkins. http://autopkgtest.ubuntu.com/ (a debci instance configured for Ubuntu) is now the (completely public) results browser for human consumption, with a web UI and a global and per-package news feed. - There are no email notifications about regressions right now. It seems most people ignored them as they produced too much noise due to flaky tests or infrastructure (and us retrying them), and they also notified the wrong person (the uploader of the package with broken tests, not the uploader of the package which caused the tests to break). Bringing this back is being worked on, but for now I'll ping responsible people directly (I. e. what I've already done already anyway for a long time). - debci also produces machine readable JSON status files for every package, run, and a global packages.json for a whole release/arch, for example: http://autopkgtest.ubuntu.com/data/status/wily/amd64/packages.json - If you run some automation/reporting on top of autopkgtest data (like the kernel team does), you are welcome to use the above JSON files, but I highly recommend querying the results from swift directly. The Swift API [2] offers reasonably flexible querying with plain/JSON/XML output, and unlike debci (which changes every now and then) the container format won't change. Please get in touch with me if you want to build/update reporting from this data. Next steps == - Bring back email notifications. (~ 1 week) - Add armhf/ppc64el testing. I integrated our existing testbed hardware into the new system already, so this is merely an issue of changing the britney configuration. But I want to wait until after the big gcc 5 transition to avoid creating unnecessary stumbling blocks. Note that after that, regressions on these architectures will lead to blocking the package, unlike with the old infrastructure where these arches were only informational. But as we do per-architecture regression detection now, we can start enforcing them. - Document the whole system. (~ 2 weeks) Bugs Please continue filing bugs at https://bugs.launchpad.net/auto-package-testing/ Thanks, Martin [1] https://lists.ubuntu.com/archives/ubuntu-devel-announce/2015-July/001141.html [2] http://developer.openstack.org/api-ref-objectstorage-v1.html#storage_object_services -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) signature.asc Description: Digital signature -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
proposed-migration results now contain cloud testing results
Hello all, In the past three weeks I've been working on and off on providing a new cloud-based infrastructure for running our autopkgtests for gating -proposed in the cloud. So far we've run them on four manually administered servers in the lab, through two Jenkins instances and a rather hideous pile of hacks and tens of thousands of little state files which got rsynced in between hosts. This hasn't been very reliable nor scalable, so it's time to replace this with something much simpler and robust: We want to run the tests in temporary cloud instances (in Canonical ScalingStack), use AMQP for request/job distribution, OpenStack swift to store the result logs/artifacts, and debci to browse the results. Today I enabled this in britney, the scripts which decide whether a package in -proposed is allowed to enter the development series. I'm sure most of you have seen this report before: http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html The new thing is that you now see some new lines like (informational) cloud autopkgtest for kde4libs 4:4.14.6-4~ubuntu4: amd64: Pass, i386: Regression with clickable links to the results on http://autopkgtest.ubuntu.com/ . Rollout plan These cloud-based tests are now being triggered by britney in addition to the usual Jenkins results, but aren't being taken into account for the decision. This is why failures are currently shown as Regression, there is no Always failed state yet as these (informational) lines are just temporarily added into the report. This will now be on a trial run for at least two weeks (I'm on holiday next week), to compare results, shake out bugs in the infrastructure, and generally make this production ready. The biggest blocker right now is that we don't yet have enough horse power in ScalingStack to keep up with the flood (max 10 instances right now). This is being worked on, but might still take a few weeks. After this becomes sufficiently robust and scalable, we'll switch over to these as primary results, and keep the old machinery as a backup for a few weeks longer. XSS feeds - If you have some pet packages, you are welcome to subscribe to their news feeds, which will get a new item whenever the package starts failing or starts succeeding (not every individual result). E. g. http://autopkgtest.ubuntu.com/packages/u/udisks2/ has this little orange broadcast symbol after the package name heading, leading to http://autopkgtest.ubuntu.com/data/feeds/u/udisks2.xml Code If you are interested in taking a look or helping out, this is the relevant code: * debci for browsing the results, powering http://autopkgtest.ubuntu.com/ http://anonscm.debian.org/cgit/collab-maint/debci.git * autopkgtest for actually exercising the tests (we are using the ssh runner with the nova setup script): http://anonscm.debian.org/cgit/autopkgtest/autopkgtest.git * The worker which accepts test requests via AMQP, runs adt-run, and puts the results into Swift; and a script to download new results for debci (both are being integrated into debci, but right now they reside here) Plus the charms and a deploy.sh script to roll it all out into the cloud: https://git.launchpad.net/~pitti/+git/autopkgtest-cloud/ * britney, which now does direct AMQP requests and swift result downloads instead of the indirection (and much duplicated work) in lp:auto-package-testing: http://bazaar.launchpad.net/~ubuntu-release/britney/britney2-ubuntu (in particular autopkgtest.py; you can run tests with python tests/test_autopkgtest.py) Bugs If you encounter bugs, please file them here: https://bugs.launchpad.net/auto-package-testing/ This is not entirely correct as lp:auto-package-testing is the old stuff which we want to get rid of; but for bug tracking it's a good enough place. Thanks, Martin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) signature.asc Description: Digital signature -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
Call for nominations for the Technical Board
Hello Ubuntu developers, The current 2-year term of the Technical Board [1] is over, and it's time for electing a new one. For the next two weeks (until January 19) we are collecting nominations, then our SABDFL will shortlist the candidates and confirm their candidacy with them, and finally the shortlist will be put to a vote by ~ubuntu-dev. Anyone from the Ubuntu community can nominate someone. Please send nominations (of yourself or someone else) to Mark Shuttleworth <mark.shuttlewo...@ubuntu.com> and CC: the nominee. You can optionally CC: the Technical Board mailing list[2], but as this is public, you *must* get the agreement of the nominated person before you CC: the list. The current board can be seen at [3]. Thank you, Martin Pitt p.p. Ubuntu Technical Board [1] https://wiki.ubuntu.com/TechnicalBoard [2] https://lists.ubuntu.com/mailman/listinfo/technical-board [3] https://launchpad.net/~techboard/+members -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) signature.asc Description: Digital signature -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
