TechnicalBoardAgenda
|
Size: 3476
Comment: add Linaro GCC to the agenda
|
Size: 2263
Comment: Post-meeting update
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| This page records the Agenda for the next meeting of the [[TechnicalBoard|Ubuntu Technical Board]]. Please see the [[http://www.ubuntu.com/community/processes/governance|Ubuntu Governance]] page for details on participation. | This page records the Agenda for the next meeting of the [[TechnicalBoard|Ubuntu Technical Board]]. Please see the [[https://www.ubuntu.com/about/about-ubuntu/governance|Ubuntu Governance]] page for details on participation. |
| Line 5: | Line 5: |
| The meeting schedule is available on the [[http://fridge.ubuntu.com/calendar|fridge calendar]]. We meet in channel '''#ubuntu-meeting''' on chat.freenode.net. The agenda will include the following: | The meeting schedule is available on the [[https://wiki.ubuntu.com/Fridge/Calendar|fridge calendar]]. We meet in channel '''#ubuntu-meeting''' on [[https://libera.chat/|Libera.Chat]]. |
| Line 7: | Line 7: |
| * Next meeting (2010-06-15) chair: cjwatson * Action review * Review StableReleaseUpdates policy of contacting the Technical Board regarding regressions (mdz) * Selection of the Linaro GCC for other architectures (doko) * Scan the [[https://lists.ubuntu.com/archives/technical-board/|mailing list archive]] for anything we missed * Check up on [[https://bugs.launchpad.net/ubuntu-community/+bugs?field.assignee=techboard|community bugs]] (standing item) * Select a chair for the next meeting * Summarize the meeting for TeamReports |
The next meeting is set for 2024-04-09, 20:00 London time. chair: seb128, backup: vorlon. |
| Line 16: | Line 9: |
| === Linaro GCC == | The agenda will include the following: |
| Line 18: | Line 11: |
| One outcome of the UDS ARM toolchain sessions was to use the Linaro toolchain to build Ubuntu/ARM. The Linaro GCC currently is a snapshot of the upstream 'gcc-4_4-branch' branch, with the changes found in the CodeSourcery GCC applied on top of it. Changes/patches found in the Ubuntu packaging are applied too. | * Apologies: * Action review: * ''ACTION:'' rbasak to update third party repo draft with outcomes from our recent out-of-band meeting (rbasak, 20:04) * ''ACTION:'' rbasak to open wider discussion on third-party repo policy (rbasak, 20:04) * ''ACTION:'' rbasak to draft a proposal of the DMB-proposed inactivity expiration policy for TB ratification (rbasak, 20:05) * ''ACTION:'' vorlon to look into scripting for packages in flavor-specific overlays (rbasak, 20:05) * ''ACTION:'' seb128 to continue working with SRU, AA, Release, Backporters and Security teams to document their membership process and link to it from https://wiki.ubuntu.com/TechnicalBoard#Team_Delegations (rbasak, 20:05) * Scan the [[https://lists.ubuntu.com/archives/technical-board/|mailing list archive]] for anything we missed (standing item) * Check up on [[https://bugs.launchpad.net/ubuntu-community/+bugs?field.assignee=techboard|community bugs]] and [[https://bugs.launchpad.net/techboard|techboard bugs]] (standing item) * Select a chair for the next meeting (next from https://launchpad.net/~techboard/+members) * AOB |
| Line 20: | Line 24: |
| We currently evaluate the builds of this compiler on armel, and on other architectures which are supported by the CodeSourcery GCC (i386, amd64, powerpc) to see, if the Linaro GCC could be used on other architectures as well. One of the arguments for this use is the outcome of a (partial) archive rebuild which we expect to be done next week, another argument is how the use of a branch, which is not the upstream branch, is perceived by the development community. Linaro itself is set up to work with upstreams and integrate changes directly with upstreams, so that changes which are accepted by upstream are integrated upstream in the trunks/development versions. However using the Linaro GCC might show different results than using the current upstream GCC branch, which maybe are unexpected and maybe are directly reported to the upstream project as a problem in their GCC versions. For at least ARM we will have another compiler version based on the GCC upstream version in the form of a gcc-4.4-branch package (looking like the current gcc-snapshot) package to provide a way to reproduce problems with the upstream GCC versions. Developers doing upstream development on Ubuntu may see these differences as well, and wrongly attribute them to the wrong version. Using a different compiler may move us a bit more away from Debian (although we rebuild packages anyway, and using a compiler with hardening defaults turned on). I'd like ot have some feedback, if such a move to a different compiler version for architectures other than ARM would be accepted by the TB, provided that the compiler doesn't show regressions, and considering that this compiler change maybe "alienates" Ubuntu a bit more from Debian/GCC upstream. Logs from previous meetings may be found at [[http://irclogs.ubuntu.com/]] or via [[ScribesTeam/MootBot|MootBot]]. |
Logs from previous meetings may be found at [[http://irclogs.ubuntu.com/]] or [[http://ubottu.com/meetingology/logs/ubuntu-meeting-2/]] or [[https://new.ubottu.com/meetingology/logs/ubuntu-meeting/2021/]]. Logs from older meetings are available via [[ScribesTeam/MootBot|MootBot]]. |
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 on Libera.Chat.
The next meeting is set for 2024-04-09, 20:00 London time. chair: seb128, backup: vorlon.
The agenda will include the following:
- Apologies:
- Action review:
ACTION: rbasak to update third party repo draft with outcomes from our recent out-of-band meeting (rbasak, 20:04)
ACTION: rbasak to open wider discussion on third-party repo policy (rbasak, 20:04)
ACTION: rbasak to draft a proposal of the DMB-proposed inactivity expiration policy for TB ratification (rbasak, 20:05)
ACTION: vorlon to look into scripting for packages in flavor-specific overlays (rbasak, 20:05)
ACTION: seb128 to continue working with SRU, AA, Release, Backporters and Security teams to document their membership process and link to it from https://wiki.ubuntu.com/TechnicalBoard#Team_Delegations (rbasak, 20:05)
Scan the mailing list archive for anything we missed (standing item)
Check up on community bugs and techboard bugs
(standing item)
Select a chair for the next meeting (next from https://launchpad.net/~techboard/+members)
- AOB
Logs from previous meetings may be found at http://irclogs.ubuntu.com/ or http://ubottu.com/meetingology/logs/ubuntu-meeting-2/ or https://new.ubottu.com/meetingology/logs/ubuntu-meeting/2021/. Logs from older meetings are available via MootBot.
TechnicalBoardAgenda (last edited 2024-04-23 19:10:37 by seb128)