TechnicalBoardAgenda

Differences between revisions 595 and 597 (spanning 2 versions)
Revision 595 as of 2017-03-14 16:52:56
Size: 2376
Editor: vorlon
Comment: rotate date/chairs
Revision 597 as of 2017-03-14 19:10:02
Size: 2028
Editor: vorlon
Comment: update from results of today's meeting
Deletions are marked like this. Additions are marked like this.
Line 7: Line 7:
The next meeting is set for 2017-03-14, 17:00 London time. chair: slangasek, backup: stgraber The next meeting is set for 2017-03-28, 17:00 London time. chair: stgraber, backup: infinity
Line 11: Line 11:
  * none
Line 13: Line 12:
  * ''ACTION:'' infinity to follow up with maas SRU exception   * ''ACTION:'' infinity to ask maas team to prepare SRU exception policy à la CurtinUpdates
Line 17: Line 16:
 * Ask for standing freeze exception for python2.6 and openjdk-9 package updates for xenial and yakkety to match the versions in the most recent development release. Both packages were uploaded as pre-release versions, are in universe, and not used by any package builds. Asking to update these to follow the versions from the most recent development release (doko).

This page records the Agenda for the next meeting of the Ubuntu Technical Board. Please see the Ubuntu Governance page for details on participation.

If you have a question to raise with the Board, you can reach the Technical Board members directly by e-mailing technical-board@lists.ubuntu.com. They may decide that your issue should be discussed at the next meeting, in which case they will add it to this page.

The meeting schedule is available on the fridge calendar. We meet in channel #ubuntu-meeting-2 on chat.freenode.net.

The next meeting is set for 2017-03-28, 17:00 London time. chair: stgraber, backup: infinity The agenda will include the following:

  • Apologies:
  • Action review:
    • ACTION: infinity to ask maas team to prepare SRU exception policy à la CurtinUpdates

    • ACTION: infinity to play with seed/maint-check changes on dogfood to build a new xenial release pocket for support length auditing (ETA: 16.04.2 release)

    • ACTION: slangasek to investigate getting tagged ubuntu-community bugs automatically forwarded to technical-board, and if not feasible, fall back to DMB sending signed emails to list for ACL requests

    • ACTION: slangasek to follow up to snapd-glib SRU exception request

  • [Add new agenda items above this line - include your name]
  • Scan the mailing list archive for anything we missed (standing item)

  • Check up on community bugs (standing item)

  • Select a chair for the next meeting (next from https://launchpad.net/~techboard/+members)

Logs from previous meetings may be found at http://irclogs.ubuntu.com/ or http://ubottu.com/meetingology/logs/ubuntu-meeting-2/. Logs from older meetings are available via MootBot.


CategoryUbuntuTeams

TechnicalBoardAgenda (last edited 2024-03-26 20:13:08 by racb)