Planning
7897
Comment:
|
8070
|
Deletions are marked like this. | Additions are marked like this. |
Line 22: | Line 22: |
* [[UbuntuSpec:foundations-m-upgrade-and-install-testing|Discuss testing]] | |
Line 75: | Line 76: |
* Soyuz: Native syncing via web service, to free up man-hours of archive admin time per week. |
Contents
Ideas
smoother boot splash via grub2 and a boot framebuffer (ColinWatson, ScottJamesRemnant)
Package Culling - find and aggressively deal with packages whose merges have been lagging for several releases
Finish Upstart (ScottJamesRemnant)
Have a UDS session for each track that is impacted by Upstart (e.g., Desktop, Server, Kernel, NewCore)
Refactor update-notifier - make update-notifier a more modular design (probably with vala), it has out-grown to be a update-notifier since some time (MichaelVogt)
make screenshots.ubuntu.com show ubuntu branding and add support for PPAs and archive.canonical.com (MichaelVogt)
Remove Demoted Packages on Upgrade - We need to explore the removal of demoted packages on upgrade (all, only auto-installed ones, only default installed ones, only unused... how to detect).
D-Bus Refactor of release-upgrader - discuss refactoring the release-upgrader backend as a dbus service to improve reliability/responsiveness (MichaelVogt)
- CD build speed has been creeping back up of late; attack it again
Foundations Support
As usual, Foundations will be providing Ubuntu support for the other teams. A high-level listing of projects where we likely will be involved is given in this section.
Desktop
- As part of their UNE work, Desktop may end up promoting Chromium to main
- HUGE push for Software Center
- goal: sell stuff in software center,
- goal: figure out how to deliver opportunistic apps via the software center
- finish ratings
- Big push for touch, not sure what the impact is going to be for Foundations yet, but we need to be aware of it
Design
- Wayland (no idea what state this is in upstream, and the X side of things should be desktop, but at the very least we'll need to look at how this overlaps/interacts with Plymouth);
- We probably ought to have a look-in on the multi-screen work, if it's dealing with remembering configurations for individual devices;
- Installer, first boot, upgrades, Update Manager, and Software Centre;
- System settings (maybe, depending on what this comes down to);
- Possibly keyboard indicator but it depends what they're doing (if it's just visual then probably not).
Server
The server team has listed their planning by priority; their bullet items below reflect this.
- Priority 1: Cloud cluster file system (not sure if we'll be needed for this or not)
- Priority 2: Java/JDK improvements (doko does a lot of that; Server team is getting a Java person, so this may impact us less)
- Priority 2: Support of alternate install modes
- Priority 3: Upstart conversion
Kernel
- Improved battery power support work; Foundations may need to (or be able to) assist
- synaptec multi-touch (multi-finger... not multi-touch)
- new multi-touch driver enhancements that may need work from Foundations
OEM
- TBD
Support FOR Foundations
Collect here items which we would like to see be done by other teams
Desktop
- Java Applet maintainance / development
- Stable xulrunner-1.9 interfaces when having more than one xulrunner version on the desktop (both eclipse and the icedtea6-plugin don't seem to get it right).
Launchpad
- Soyuz/IS: Rebuild tests take too long, or slow down PPA buildds.
- Soyuz: Native syncing via web service, to free up man-hours of archive admin time per week.
- Buildd configuration, and how to reproduce results from test runs on the buildds. Differences in the configuration of distro and PPA buildds. LP: 556597 as an example. Seen with some eglibc test cases as well.
QA
- TCK testing
Placeholders for Big Topics
10.04 Review - hold this early to aid breakout topics, maybe in the first roundtable
- Distributed Development
- Boot Performance/Experience
- Spring Clean (right after an LTS release is a good time for an aggressive cleanup of things we don't need or that should be extensively refactored)
- Python
Automated transition testing framework (build, run upstream unit test, 2to3, report on ftbfs and test failures, against any/every python version) (BarryWarsaw)
Eliminate symlinks for python-[central (BarryWarsaw). This is a duplicate of foundations-lucid-robust-python-packaging.
Python 2.7 (BarryWarsaw) That should be tested before UDS as a basis for a decision.
Freezing (e.g. cx_freeze) critical dist upgrade tools? (BarryWarsaw)
- Compile for i686 as the default on i386 (instead of i486).
Lucid specs not done
(Numbers in parentheses indicate to-do/postponed/done.)
desktop-lucid-language-selector (0/1/1)
foundations-lucid-daily-builds (1/0/10)
foundations-lucid-software-raid-in-ubiquity-for-desktop-install (0/7/7)
security-lucid-catchall-medium (0/0/1)
Lucid specs partly done
foundations-lucid-apt-python-apt-network-error-handling (2/0/7)
foundations-lucid-lts-upgrades (14/0/24)
foundations-lucid-software-center-history-of-packaging-transactions (4/2/9)
Lucid specs mostly done
FoundationsTeam/Maverick/Planning (last edited 2010-05-04 14:04:46 by p5B09F55E)