CoreDevApplication

Differences between revisions 6 and 12 (spanning 6 versions)
Revision 6 as of 2025-06-25 09:33:40
Size: 14268
Editor: hyask
Comment:
Revision 12 as of 2025-09-26 10:34:04
Size: 30353
Editor: hyask
Comment:
Deletions are marked like this. Additions are marked like this.
Line 15: Line 15:
 * I'd like to be able to push some improvements to tools like MoM.
 * I'd like to be able to help more effectively during +1 maintenance shifts, that I enjoy particularly.
 * I'm aware that this is a straight to core-dev application, but this is what I need to actually better help the Ubuntu release process, and I would have a hard time justifying a PPU application. Also, MOTU wouldn't actually help me much, given the majority of my uploads, and particularly the ones that are part of my release work, are in {{{main}}}.
Line 35: Line 35:
 * TODO: triage those
 * 2024-02-13 - Ubuntu Mantic - [[https://launchpad.net/ubuntu/+source/autopkgtest/5.32ubuntu3~23.10.1|autopkgtest/5.32ubuntu3~23.10.1]]
 * 2023-12-15 - Ubuntu Noble - [[https://launchpad.net/ubuntu/+source/klibc/2.0.13-2ubuntu1|klibc/2.0.13-2ubuntu1]]

* https://bugs.launchpad.net/ubuntu/+source/beets/+bug/2106276
* https://bugs.launchpad.net/ubuntu/+source/beets/+bug/2107317 (https://salsa.debian.org/python-team/packages/beets/-/merge_requests/3)

CDimage stuff:
https://code.launchpad.net/~hyask/ubuntu-cdimage/+git/ubuntu-cdimage/+merge/484314
TODO: add also ubuntu-release-tools, ubuntu-archive-tools, etc...
Exhaustive list of my uploads is available here:
 * Launchpad: https://launchpad.net/~hyask/+uploaded-packages
 * UDD: https://udd.debian.org/cgi-bin/ubuntu-sponsorships.cgi?render=html&sponsor=&sponsor_search=name&sponsoree=*Skia*&sponsoree_search=name

Below is a selection of those with some quick description and pointers, to make it easier to get an idea of my work. Please ask me about specific uploads that picks your interest and are not in the list.
Line 48: Line 44:
 * {{{beets}}} - s390x test failure
   * Interesting full story of a patch produced for Ubuntu, then sent out in both Debian and upstream repos, then came back with a sync.
   * Debian PR: https://salsa.debian.org/python-team/packages/beets/-/merge_requests/3
   * Upstream PR: https://github.com/beetbox/beets/pull/5708
   * bug: https://bugs.launchpad.net/ubuntu/+source/beets/+bug/2106276
   * git-ubuntu MP: https://code.launchpad.net/~hyask/ubuntu/+source/beets/+git/beets/+merge/483930
   * 2025-04-09 - Ubuntu Plucky - [[https://launchpad.net/ubuntu/+source/beets/2.2.0-2ubuntu1|beets/2.2.0-2ubuntu1]]
   * sync bug: https://bugs.launchpad.net/ubuntu/+source/beets/+bug/2107317
Line 49: Line 53:
   * This one counts as FFe too, mentioned below.
   * This one is interestingly a native package.
   * This shows some lintian related improvements to the package.
   * MP: https://code.launchpad.net/~hyask/whoopsie/+git/whoopsie/+merge/482986
   * bug: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/2103526
Line 50: Line 59:
   * This one counts as FFe too, mentioned below
   * bug: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/2103526
Line 53: Line 60:
   * 2024-10-07 - Ubuntu Oracular - [[https://launchpad.net/ubuntu/+source/base-files/13.3ubuntu6|base-files/13.3ubuntu6]]
Line 56: Line 62:
   * 2024-10-07 - Ubuntu Oracular - [[https://launchpad.net/ubuntu/+source/base-files/13.3ubuntu6|base-files/13.3ubuntu6]]
Line 57: Line 64:
   * This one is interestingly a native package, which was obviously out of sync between the archive and the repo.
   * bug: https://bugs.launchpad.net/whoopsie/+bug/2081271
   * MP: https://code.launchpad.net/~hyask/whoopsie/+git/whoopsie/+merge/473530
Line 58: Line 68:
   * bug: https://bugs.launchpad.net/whoopsie/+bug/2081271
Line 60: Line 69:
   * 2024-07-30 - Ubuntu Oracular - [[https://launchpad.net/ubuntu/+source/autopkgtest/5.37ubuntu4|autopkgtest/5.37ubuntu4]]
Line 63: Line 71:
   * 2024-07-30 - Ubuntu Oracular - [[https://launchpad.net/ubuntu/+source/autopkgtest/5.37ubuntu4|autopkgtest/5.37ubuntu4]]
Line 64: Line 73:
   * 2024-04-19 - Ubuntu Noble - [[https://launchpad.net/ubuntu/+source/apt-clone/0.4.3+nmu2ubuntu2|apt-clone/0.4.3+nmu2ubuntu2]]
Line 68: Line 76:
   * 2024-04-19 - Ubuntu Noble - [[https://launchpad.net/ubuntu/+source/apt-clone/0.4.3+nmu2ubuntu2|apt-clone/0.4.3+nmu2ubuntu2]]
 * {{{klibc}}} - fixing autopkgtests
   * My very first upload, nothing particular of note that I remember.
   * bug: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/2046336
   * 2023-12-15 - Ubuntu Noble - [[https://launchpad.net/ubuntu/+source/klibc/2.0.13-2ubuntu1|klibc/2.0.13-2ubuntu1]]
Line 71: Line 85:
 * {{{open-iscsi}}} merge
   * autopkgtest had to be fixed from two different perspectives:
     * https://git.launchpad.net/~hyask/ubuntu/+source/open-iscsi/commit/?id=d65d8fa5a47a0ec32e493012a1fa213bf628fd34
     * https://git.launchpad.net/~hyask/ubuntu/+source/open-iscsi/commit/?id=fe0be07ac2de3b5710f8c33c40c050fcbb6c51c2
   * bug: https://bugs.launchpad.net/ubuntu/+source/open-iscsi/+bug/2110454
   * git-ubuntu MP: https://code.launchpad.net/~hyask/ubuntu/+source/open-iscsi/+git/open-iscsi/+merge/488607
   * 2025-07-10 - Ubuntu Questing - [[https://launchpad.net/ubuntu/+source/open-iscsi/2.1.11-1ubuntu1|2.1.11-1ubuntu1]]
 * {{{nfs-utils}}} merge
   * Very simple rebase, nothing of note.
   * bug: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/2112047
   * git-ubuntu MP: https://code.launchpad.net/~hyask/ubuntu/+source/nfs-utils/+git/nfs-utils/+merge/488018
   * 2025-07-01 - Ubuntu Questing - [[https://launchpad.net/ubuntu/+source/nfs-utils/1:2.8.3-1ubuntu1|1:2.8.3-1ubuntu1]]
 * {{{bpftrace}}} merge
   * Quite complex merge with some changes along the way, see changelog for full story.
   * Most of the changes revolved around the autopkgtests, because that's the main cause for the delta in the first place.
   * Also needed to get unstuck from -proposed with an Archive Admin, to promote {{{libclang1-20}}} to {{{main}}}.
   * bug: https://bugs.launchpad.net/ubuntu/+source/bpftrace/+bug/2111982
   * git-ubuntu MP: https://code.launchpad.net/~hyask/ubuntu/+source/bpftrace/+git/bpftrace/+merge/487771
   * 2025-07-01 - Ubuntu Questing - [[https://launchpad.net/ubuntu/+source/bpftrace/0.23.2-1ubuntu1|0.23.2-1ubuntu1]]
 * {{{pcb-rnd}}} sync
   * Sync'd ten days after delta was introduced, and Debian caught up with upstream.
   * bug: https://bugs.launchpad.net/ubuntu/+source/pcb-rnd/+bug/2115481
   * 2025-06-27 - Ubuntu Questing - [[https://launchpad.net/ubuntu/+source/pcb-rnd/3.1.7b-1|3.1.7b-1]]
Line 72: Line 109:
   * 2025-04-09 - Ubuntu Plucky - [[https://bugs.launchpad.net/ubuntu/+source/apt-clone/+bug/2106470|apt-clone/0.5.3+nmu3 sync]]
Line 74: Line 110:
   * 2025-04-09 - Ubuntu Plucky - [[https://bugs.launchpad.net/ubuntu/+source/apt-clone/+bug/2106470|apt-clone/0.5.3+nmu3]]
Line 75: Line 112:
   * 2025-02-19 - Ubuntu Plucky - [[https://launchpad.net/ubuntu/+source/kbd/2.7.1-2ubuntu1|kbd/2.7.1-2ubuntu1 merge]]
Line 77: Line 113:
   * git-ubuntu MP: https://code.launchpad.net/~hyask/ubuntu/+source/kbd/+git/kbd/+merge/481541
   * 2025-02-19 - Ubuntu Plucky - [[https://launchpad.net/ubuntu/+source/kbd/2.7.1-2ubuntu1|kbd/2.7.1-2ubuntu1]]
Line 78: Line 116:
   * 2025-01-13 - Ubuntu Plucky - [[https://launchpad.net/ubuntu/+source/shadow/1:4.16.0-7ubuntu1|shadow/1:4.16.0-7ubuntu1 merge]]
Line 81: Line 118:
   * git-ubuntu MP: https://code.launchpad.net/~hyask/ubuntu/+source/shadow/+git/shadow/+merge/477650
   * 2025-01-13 - Ubuntu Plucky - [[https://launchpad.net/ubuntu/+source/shadow/1:4.16.0-7ubuntu1|shadow/1:4.16.0-7ubuntu1]]
Line 82: Line 121:
   * 2025-01-13 - Ubuntu Plucky - [[https://launchpad.net/ubuntu/+source/util-linux/2.40.2-14ubuntu1|util-linux/2.40.2-14ubuntu1 merge]]
Line 85: Line 123:
   * git-ubuntu MP: https://code.launchpad.net/~hyask/ubuntu/+source/util-linux/+git/util-linux/+merge/478455
   * 2025-01-13 - Ubuntu Plucky - [[https://launchpad.net/ubuntu/+source/util-linux/2.40.2-14ubuntu1|util-linux/2.40.2-14ubuntu1]]
Line 88: Line 129:
 * SRU documentation:
   * Sparked after opening a {{{regression-update}}} bug (https://bugs.launchpad.net/auto-upgrade-testing/+bug/2115731)
   * Updated the {{{autopkgtest}}} special case test plan
   * https://code.launchpad.net/~hyask/sru-docs/+git/sru-docs/+merge/488081
Line 89: Line 134:
   * 2025-03-03 - Ubuntu Jammy - [[https://launchpad.net/ubuntu/+source/libapache2-mod-python/3.5.0+git20211031-0ubuntu3|libapache2-mod-python/3.5.0+git20211031-0ubuntu3]]
Line 92: Line 136:
   * git-ubuntu MP: https://code.launchpad.net/~hyask/ubuntu/+source/libapache2-mod-python/+git/libapache2-mod-python/+merge/482125
   * 2025-03-03 - Ubuntu Jammy - [[https://launchpad.net/ubuntu/+source/libapache2-mod-python/3.5.0+git20211031-0ubuntu3|libapache2-mod-python/3.5.0+git20211031-0ubuntu3]]
Line 93: Line 139:
   * bug: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/2097469
   * git-ubuntu MP: https://code.launchpad.net/~hyask/ubuntu/+source/base-files/+git/base-files/+merge/480705
Line 94: Line 142:
   * bug: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/2097469
Line 96: Line 143:
   * 2025-01-27 - Ubuntu Noble - [[https://launchpad.net/ubuntu/+source/python-apt/2.7.7ubuntu4|python-apt/2.7.7ubuntu4]]
Line 99: Line 145:
   * git-ubuntu MP: https://code.launchpad.net/~hyask/ubuntu/+source/python-apt/+git/python-apt/+merge/480150
   * 2025-01-27 - Ubuntu Noble - [[https://launchpad.net/ubuntu/+source/python-apt/2.7.7ubuntu4|python-apt/2.7.7ubuntu4]]
Line 100: Line 148:
   * Pretty boring buffer overflow issue. One notable part is that this was apparently reported in 2018 as a CVE: https://nvd.nist.gov/vuln/detail/CVE-2018-13410
   * Submitted to Debian and uploaded.
   * Added a DEP8 test along the way.
   * SRU bug: https://bugs.launchpad.net/ubuntu/+source/zip/+bug/2093024
   * git-ubuntu MP against devel: https://code.launchpad.net/~hyask/ubuntu/+source/zip/+git/zip/+merge/479674
   * git-ubuntu MP against oracular: https://code.launchpad.net/~hyask/ubuntu/+source/zip/+git/zip/+merge/479896
   * git-ubuntu MP against noble: https://code.launchpad.net/~hyask/ubuntu/+source/zip/+git/zip/+merge/479897
Line 103: Line 158:
   * SRU bug: https://bugs.launchpad.net/ubuntu/+source/zip/+bug/2093024
   * Pretty boring buffer overflow issue. One notable part is that this was apparently reported in 2018 as a CVE: https://nvd.nist.gov/vuln/detail/CVE-2018-13410
   * Submitted to Debian and uploaded
Line 107: Line 159:
   * Special SRU exception: https://wiki.ubuntu.com/StableReleaseUpdates#autopkgtest
   * SRU bug: https://bugs.launchpad.net/ubuntu/+source/autopkgtest/+bug/2071609
Line 109: Line 163:
   * SRU bug: https://bugs.launchpad.net/ubuntu/+source/autopkgtest/+bug/2071609
   * Special SRU exception: https://wiki.ubuntu.com/StableReleaseUpdates#autopkgtest
 * {{{autopkgtest}}} new release
   * SRU bug: https://bugs.launchpad.net/ubuntu/+source/autopkgtest/+bug/2051939
   * 2024-02-13 - Ubuntu Mantic - [[https://launchpad.net/ubuntu/+source/autopkgtest/5.32ubuntu3~23.10.1|autopkgtest/5.32ubuntu3~23.10.1]]
   * 2024-02-13 - Ubuntu Jammy - [[https://launchpad.net/ubuntu/+source/autopkgtest/5.32ubuntu3~22.04.1|autopkgtest/5.32ubuntu3~22.04.1]]
Line 115: Line 171:
 * {{{bpftrace}}} had its testsuite running, but logging was a bit poor in case of issue
   * TODO document this
 * {{{util-linux}}} recently started shipping the `login` binary package.
   * TODO document this
 * Yes, I do run some tests 🙃: https://autopkgtest.ubuntu.com/user/hyask/?only-results=true&limit=4000
 * {{{open-iscsi}}} has some interesting tests that had issue.
   * They also make use of some environment variable specific to the Ubuntu infrastructure.
   * See the "Package Merges" section for the links to fixes.
 * {{{bpftrace}}} had its testsuite running, but logging was a bit poor.
   * In case of issue, , so I improved things by adding {{{CTEST_OUTPUT_ON_FAILURE=ON}}}.
   * See "Merge" section above
 * {{{util-linux}}} recently started shipping the `login` binary package, but lacked tests.
   * See the "Working with upstream" section, because the test I've wrote and submitted went straight to Debian.
Line 120: Line 181:
   * TODO document this    * See zip SRU in section above, I've added a DEP8 test along with the bugfix.
Line 125: Line 186:
Line 134: Line 196:
Line 136: Line 199:
TODO: make some more
I've never driven a full transition all by myself, but I've helped out a few that I saw passing by:

 * {{{rails 7}}}
   * (Re)triggered some autopkgtests with right combination of triggers, or sometimes after a Debian autosync happened:
     * {{{ruby-actionpack-xml-parser}}}: https://autopkgtest.ubuntu.com/packages/r/ruby-actionpack-xml-parser
     * {{{ruby-globalid}}}: https://autopkgtest.ubuntu.com/packages/r/ruby-globalid
   * Removed {{{ruby-sassc-rails}}}: https://bugs.launchpad.net/ubuntu/+source/ruby-sassc-rails/+bug/2116076
   * Removed {{{ruby-sass-rails}}}: https://bugs.launchpad.net/ubuntu/+source/ruby-sass-rails/+bug/2116095
   * Removed {{{ruby-ammeter}}}: https://bugs.launchpad.net/ubuntu/+source/ruby-ammeter/+bug/2116080
   * Removed {{{ruby-activerecord-import}}}: https://bugs.launchpad.net/ubuntu/+source/ruby-activerecord-import/+bug/2116082
   * Removed {{{ruby-rails-deprecated-sanitizer}}}: https://bugs.launchpad.net/ubuntu/+source/ruby-rails-deprecated-sanitizer/+bug/2116096
   * Fixed the {{{ruby-omniauth-rails-csrf-protection}}} autopkgtests, by packaging a new upstream version and uploading it to Debian:
     * RFS: https://lists.debian.org/debian-ruby/2025/07/msg00000.html
Line 139: Line 213:
   * Helped the {{{alberta}}} transition from {{{libalberta4t64}}} to {{{libalberta5}}} by fixing the last remaining dependency: {{{dune-grid}}}.
   * bug: https://bugs.launchpad.net/ubuntu/+source/dune-grid/+bug/2114917
   * git-ubuntu MP: [[https://code.launchpad.net/~hyask/ubuntu/+source/dune-common/+git/dune-common/+merge/487436]]
Line 140: Line 217:
   * Helped the {{{alberta}}} transition from {{{libalberta4t64}}} to {{{libalberta5}}} by fixing the last remaining dependency: {{{dune-grid}}}.
   * git-ubuntu MP: [[https://code.launchpad.net/~hyask/ubuntu/+source/dune-common/+git/dune-common/+merge/487436]]
   * bug: https://bugs.launchpad.net/ubuntu/+source/dune-grid/+bug/2114917
Line 147: Line 221:
Line 151: Line 226:
     * bug: https://bugs.launchpad.net/ubuntu/+source/capnproto/+bug/2063194
Line 152: Line 228:
     * bug: https://bugs.launchpad.net/ubuntu/+source/capnproto/+bug/2063194
Line 155: Line 230:
     * bug: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/2103526
Line 156: Line 232:
     * https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/2103526
Line 161: Line 236:
Line 163: Line 239:

* 2025, week 25: https://discourse.ubuntu.com/t/1-maintenance-report-week-25-2025/63166
 * 2025, week 25: https://discourse.ubuntu.com/t/1-maintenance-report-week-25-2025/63166
   * Uploaded four packages:
     * {{{pcb-rnd}}} amd64 FTBFS (MP: https://code.launchpad.net/~hyask/ubuntu/+source/pcb-rnd/+git/pcb-rnd/+merge/487210)
     * {{{opensmtpd-table-mysql}}} FTBFS (MP: https://code.launchpad.net/~hyask/ubuntu/+source/opensmtpd-table-mysql/+git/opensmtpd-table-mysql/+merge/487281)
     * {{{dune-common}}} ppc64el FTBFS (MP: https://code.launchpad.net/~hyask/ubuntu/+source/dune-common/+git/dune-common/+merge/487436)
     * {{{linuxcnc}}} merge (MP: https://code.launchpad.net/~hyask/ubuntu/+source/linuxcnc/+git/linuxcnc/+merge/487358)
Line 168: Line 249:
 * {{{util-linux}}} - opt-in re-review after a merge  * {{{util-linux}}} - after a merge, bin:util-linux started to depend on bin:liblastlog2-2 which was in Universe
   * Wasn't strictly necessary because of the "renamed of reorganized source" policy.
   * This ended up being an opt-in re-review, which is good to improve the overall quality of Ubuntu.
Line 170: Line 253:
   * I still need to follow-up acting on the feedback there.
Line 171: Line 255:
   * It fell under the particular case of having {{{retry}}} only in the jammy-release pocket, so couldn't be updated. This required a new upload to reach jammy-updates and then get promoted to {{{main}}}.
   * MIR bug: https://bugs.launchpad.net/ubuntu/+source/retry/+bug/2076381
   * SRU bug: https://bugs.launchpad.net/ubuntu/+source/retry/+bug/2080616
Line 173: Line 260:
   * MIR bug: https://bugs.launchpad.net/ubuntu/+source/retry/+bug/2076381
   * SRU bug: https://bugs.launchpad.net/ubuntu/+source/retry/+bug/2080616
   * It fell under the particular case of having {{{retry}}} only in the jammy-release pocket, so couldn't be updated. This required a new upload to reach jammy-updates and then get promoted to {{{main}}}.
 * {{{mmdebstrap}}} - there was an attempt, unfortunately unsuccessful because of [[https://bugs.launchpad.net/ubuntu/+source/mmdebstrap/+bug/2087937/comments/6|a few reasons]].
Line 179: Line 265:
 * 2025-03-19 - Ubuntu Plucky - https://code.launchpad.net/~hyask/ubuntu-seeds/+git/ubuntu-seeds/+merge/483070
   * Simple update of {{{ship-live}}} for ARM laptops
 * Simple update of {{{ship-live}}} for ARM laptops
  
* 2025-03-19 - Ubuntu Plucky - https://code.launchpad.net/~hyask/ubuntu-seeds/+git/ubuntu-seeds/+merge/483070
Line 183: Line 269:
Line 188: Line 275:
   * Story above, in the "Feature and bugfix uploads" section.
Line 199: Line 287:
 * My +1 maintenance section also has examples of this.
 * I also maintain the [[https://tracker.debian.org/pkg/rust-swaysome|Debian swaysome package]].
Line 202: Line 293:
 * {{{osinfo-db}}}:
   * Updated a bunch of Ubuntu links: https://gitlab.com/libosinfo/osinfo-db/-/merge_requests/847
Line 203: Line 296:
   * Story above, in the "Feature and bugfix uploads" section.
Line 209: Line 303:
 * My +1 maintenance section also has examples of this.
Line 212: Line 308:
TODO

=== Bug Triage ===

 * Regular Foundations bug triage:
   * TODO: describe and link that work
Alongside packaging work, I'm also involved in many other things around infrastructure and Ubuntu tooling:
 * I've led the Noble .2 release checklist.
 * I've already send out announcement emails:
   * the Noble .2 announcement: https://lists.ubuntu.com/archives/ubuntu-announce/2025-February/000308.html
   * the Focal EOSS email: https://lists.ubuntu.com/archives/ubuntu-announce/2025-April/000310.html
 * I'm active on Matrix helping out coordinating release work in general.
 * I've helped review a bunch of FFes since the Plucky cycle. Here are some recent examples:
   * An OpenStack python dependency, with a huge version bump: https://bugs.launchpad.net/ubuntu/+source/python-pysnmp4/+bug/2125509
     I've actually asked @ginggs whether or not this should be granted, given how on edge this one was.
   * Stubble kernel on arm64 questing images: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/2121352
   * A late sudo merge for Questing. This one actually has me making a mistake, and amending it 🙃: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/2125486
   * Ubuntu insight for desktop questing images: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2121164
 * I've helped out during some archive openings:
   * Plucky: https://warthogs.atlassian.net/browse/RTMP-2068
   * Questing: https://warthogs.atlassian.net/browse/RTMP-2428
 * I'm currently maintaining the Error Tracker (https://errors.ubuntu.com):
   * See my activities there:
     * https://code.launchpad.net/~daisy-pluckers/daisy/trunk
     * https://code.launchpad.net/~daisy-pluckers/errors/trunk
   * I'm also working on modernizing things in this repo: https://github.com/ubuntu/error-tracker
 * A selection of work on {{{ubuntu-cdimage}}}:
   * Decouple sstream from publishing: https://code.launchpad.net/~hyask/ubuntu-cdimage/+git/ubuntu-cdimage/+merge/484510
   * Stop prompting for oversized images: https://code.launchpad.net/~hyask/ubuntu-cdimage/+git/ubuntu-cdimage/+merge/484495
   * Remove Ubuntu Base i386 image: https://code.launchpad.net/~hyask/ubuntu-cdimage/+git/ubuntu-cdimage/+merge/484611
   * Some {{{riscv64}}} images fix, plus added tests: https://code.launchpad.net/~hyask/ubuntu-cdimage/+git/ubuntu-cdimage/+merge/484314
 * A selection of work on {{{ubuntu-release-tools}}}:
   * Some release checklist template improvements: https://code.launchpad.net/~hyask/ubuntu-release-tools/+git/ubuntu-release-tools/+merge/483228
   * Flavors move to Matrix: https://code.launchpad.net/~hyask/ubuntu-release-tools/+git/ubuntu-release-tools/+merge/475628
   * Updated some announcements: https://code.launchpad.net/~hyask/ubuntu-release-tools/+git/ubuntu-release-tools/+merge/481710
 * A selection of work on {{{meta-release}}}:
   * Big work to add automated validation and CI: https://code.launchpad.net/~hyask/meta-release/+git/meta-release/+merge/474070
   * Release Oracular: https://code.launchpad.net/~hyask/meta-release/+git/meta-release/+merge/474869
 * A selection of work on {{{ubuntu-archive-tools}}}:
   * Some improvements on {{{phased-updater}}}: https://code.launchpad.net/~hyask/ubuntu-archive-tools/+git/ubuntu-archive-tools/+merge/472901
   * Improved logging in {{{isotracker}}} related code: https://code.launchpad.net/~hyask/ubuntu-archive-tools/+git/ubuntu-archive-tools/+merge/484301
   * Improved {{{--help}}} in {{{retry-autopkgtest-regressions}}}: https://code.launchpad.net/~hyask/ubuntu-archive-tools/+git/ubuntu-archive-tools/+merge/480070
 * A selection of work on {{{ubuntu-dev-tools}}}:
   * Fixing a bug in {{{import-bug-from-debian}}}: https://code.launchpad.net/~hyask/ubuntu-dev-tools/+git/ubuntu-dev-tools/+merge/468091
 * A selection of work on {{{command-not-found-extractor}}}:
   * Fixing the extractor triggering OOM-kill in various ways:
     * https://code.launchpad.net/~hyask/command-not-found-extractor/+git/command-not-found-extractor/+merge/483631
     * https://code.launchpad.net/~hyask/command-not-found-extractor/+git/command-not-found-extractor/+merge/492711


=== Bug Triage and reporting ===

I'm often exposed to bugs, either directly or indirectly through colleagues hitting them, so I try to report them as much as possible:
Just a few examples:

 * https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2085147
 * https://bugs.launchpad.net/ubuntu/noble/+source/autopkgtest/+bug/2049529
 * https://bugs.launchpad.net/ubuntu/+source/autopkgtest/+bug/2075166


As part of Foundations, I'm subscribed to a number of packages where I receive bugs and triage them.
Just a few examples:

 * https://bugs.launchpad.net/ubuntu/+source/boot-managed-by-snapd/+bug/2096979/comments/9
 * https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2099811/comments/4
 * https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2098093/comments/4
Line 221: Line 371:
Since I'm working for Canonical, in the Ubuntu Release Management Team (Foundations), I'm very much involved with the release process of Ubuntu as a whole. In the past, I've also been involved in the maintenance of the autopkgtest.u.c infrastructure, and the tooling around that.
In the coming future, I'd like to help automate as much as possible the release process, so that it's self-documented as code, and not tribal knowledge in people's head anymore.

On my free time, which I don't have much, I like maintaining and improving [[https://gitlab.com/hyask/swaysome|swaysome]], and give a hand hosting [[https://threadandneedles.org/|Thread and Needles]]. I also like to maintain and improve my lovely [[https://hya.sk/|little space of the Internet]], as well as my self-hosted NAS running --(Armbian)-- Ubuntu. As always, side projects come and go, but I generally like hacking and DIY many things more or less always related to free software.
Line 224: Line 378:
There are a few things I'd like to improve:

 * Write more bug reports. It's often that I have a few things hitting me on my machine, but it's way too often that I just workaround and forget about the problem, where I could actually spend time fixing things for real.
 * Take some time to improve my tooling and workflow. It's way too easy to get stuck with doing/using what I know, when sometimes there is a nice process/tool I see used by someone else, and would like to adopt it, but never get to it.
Line 229: Line 387:
 * Reach a state where one clicks a button and releases Ubuntu. That's a long shot, and there will always be some manual steps involved, but targeting that will bring many improvements already.
 * Help out set up what's needed to have nicer testing, especially around GUI. There is already ongoing work for that, but this will need integration, and a lot of work to have testsuites for everything. I'd like to give a hand, especially to flavors, to have them catch the train and improve the QA of the whole ecosystem.
Line 231: Line 392:
 * Things are improving (a lot!), but the tooling is always a pain. On the top of my head, I could think of {{{bzr}}}, Launchpad's merge view, the seeds file format (wiki syntax, seriously???), the ubuntu-cdimage story, etc...
 * To compensate Launchpad being Launchpad, many repos within the Ubuntu world have moved to Github. While this brings nice modern features, it also reduces the integration of everything, like Ubuntu bugs, and sometimes makes it harder to discover where sources are hosted. I'm also wondering what would happen if Microsoft Github went down (or else, given current geopolitical context), regarding releasing Ubuntu, since some important repos are hosted there (like [[https://github.com/canonical/models|the models]]).

I, Skia, hereby apply for core-dev.

Name

Florent 'Skia' Jacquet

Launchpad Page

https://launchpad.net/~hyask

Wiki Page

https://wiki.ubuntu.com/skia/


I am applying because:

  • I'd like to be able to officially join the Release Team.
  • I'd like to help smoothen the release process by being able to upload some bits by myself.
  • I'd like to be able to help more effectively during +1 maintenance shifts, that I enjoy particularly.
  • I'm aware that this is a straight to core-dev application, but this is what I need to actually better help the Ubuntu release process, and I would have a hard time justifying a PPU application. Also, MOTU wouldn't actually help me much, given the majority of my uploads, and particularly the ones that are part of my release work, are in main.

Who I am

This is almost plain copy-paste from my Contributing Developer application, given that the story hasn't changed.

My name is Florent Jacquet, but just call me Skia, even IRL, as everyone does.

I first installed Xubuntu 7.10 alternate edition on a 64MB RAM machine in 2008. The machine was already 10 years old by that time, but the lightweight system made it usable again, and it was great! Since then, I’ve installed a lot of {X,K,}Ubuntu on all my relative’s machines: parents, grand-parents, uncles, cousins, high-school companions, high school’s machines themselves, university friends and associations, you name it. I’ve personally distro-hoped for a while, but always kept either Debian or Ubuntu on my servers or machines that I wanted stable.

I now work since 2023-10-31 for Canonical as part of Foundations/Ubuntu QA/Release Management team.

My Ubuntu story

My involvement

Examples of my work / Things I'm proud of

Exhaustive list of my uploads is available here:

Below is a selection of those with some quick description and pointers, to make it easier to get an idea of my work. Please ask me about specific uploads that picks your interest and are not in the list.

Feature and bugfix uploads

Package Merges and Syncs

SRUs

Autopkgtest & DEP8

Proposed Migrations

Transitions

I've never driven a full transition all by myself, but I've helped out a few that I saw passing by:

Milestones and Exceptions

+1 maintenance

MIRs

Seed Operations

Working with upstream

Debian

Upstream projects

Misc

Alongside packaging work, I'm also involved in many other things around infrastructure and Ubuntu tooling:

Bug Triage and reporting

I'm often exposed to bugs, either directly or indirectly through colleagues hitting them, so I try to report them as much as possible: Just a few examples:

As part of Foundations, I'm subscribed to a number of packages where I receive bugs and triage them. Just a few examples:

Areas of work

Since I'm working for Canonical, in the Ubuntu Release Management Team (Foundations), I'm very much involved with the release process of Ubuntu as a whole. In the past, I've also been involved in the maintenance of the autopkgtest.u.c infrastructure, and the tooling around that. In the coming future, I'd like to help automate as much as possible the release process, so that it's self-documented as code, and not tribal knowledge in people's head anymore.

On my free time, which I don't have much, I like maintaining and improving swaysome, and give a hand hosting Thread and Needles. I also like to maintain and improve my lovely little space of the Internet, as well as my self-hosted NAS running Armbian Ubuntu. As always, side projects come and go, but I generally like hacking and DIY many things more or less always related to free software.

Things I could do better

There are a few things I'd like to improve:

  • Write more bug reports. It's often that I have a few things hitting me on my machine, but it's way too often that I just workaround and forget about the problem, where I could actually spend time fixing things for real.
  • Take some time to improve my tooling and workflow. It's way too easy to get stuck with doing/using what I know, when sometimes there is a nice process/tool I see used by someone else, and would like to adopt it, but never get to it.

Plans for the future

General

  • Reach a state where one clicks a button and releases Ubuntu. That's a long shot, and there will always be some manual steps involved, but targeting that will bring many improvements already.
  • Help out set up what's needed to have nicer testing, especially around GUI. There is already ongoing work for that, but this will need integration, and a lot of work to have testsuites for everything. I'd like to give a hand, especially to flavors, to have them catch the train and improve the QA of the whole ecosystem.

What I like least in Ubuntu

  • Things are improving (a lot!), but the tooling is always a pain. On the top of my head, I could think of bzr, Launchpad's merge view, the seeds file format (wiki syntax, seriously???), the ubuntu-cdimage story, etc...

  • To compensate Launchpad being Launchpad, many repos within the Ubuntu world have moved to Github. While this brings nice modern features, it also reduces the integration of everything, like Ubuntu bugs, and sometimes makes it harder to discover where sources are hosted. I'm also wondering what would happen if Microsoft Github went down (or else, given current geopolitical context), regarding releasing Ubuntu, since some important repos are hosted there (like the models).


Comments

If you'd like to comment, but are not the applicant or a sponsor, do it here. Don't forget to sign with @SIG@.


Endorsements

TEMPLATE

== <SPONSORS NAME> ==
=== General feedback ===
## Please fill us in on your shared experience. (How many packages did you sponsor? How would you judge the quality? How would you describe the improvements? Do you trust the applicant?)

=== Specific Experiences of working together ===
''Please add good examples of your work together, but also cases that could have handled better.''
## Full list of sponsored packages can be generated here:
##  https://udd.debian.org/cgi-bin/ubuntu-sponsorships.cgi
=== Areas of Improvement ===

CategoryCoreDevApplication

skia/CoreDevApplication (last edited 2025-09-29 09:48:10 by seb128)