Planning

Differences between revisions 1 and 26 (spanning 25 versions)
Revision 1 as of 2010-04-06 15:58:40
Size: 2562
Editor: 82-69-40-219
Comment: move from internal wiki
Revision 26 as of 2010-04-21 17:28:26
Size: 5677
Editor: c-71-56-223-2
Comment:
Deletions are marked like this. Additions are marked like this.
Line 3: Line 3:
 * move CD booting to grub2/gfxterm (ColinWatson)
 * smoother boot splash via grub2/efifb (ColinWatson, ScottJamesRemnant)
 * multiarch redux
 * find and aggressively deal with packages whose merges have been lagging for several releases
 * finish Upstart (ScottJamesRemnant)
 * Implement the [[https://docs.google.com/a/canonical.com/Doc?docid=0AU5sFuLRpCpBZGZra2pqY2pfMTAxZ25rcnBnNXY&hl=en|installer redesign spec]] (EvanDandrea)
 * make update-notifier a more modular design (probably with vala), it has out-grown to be a update-notifier since some time (MichaelVogt)
 * [[UbuntuSpec:foundations-m-cd-boot|move CD booting to grub2/gfxterm]] (ColinWatson)
 * [[UbuntuSpec:foundations-maverick-grub2-boot-framebuffer|smoother boot splash via grub2 and a boot framebuffer]] (ColinWatson, ScottJamesRemnant)
 * [[UbuntuSpec:foundation-m-multiarch-redux|Multiarch Redux]]
 * [[UbuntuSpec:foundations-m-package-culling|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)
   * [[UbuntuSpec:foundations-m-upstart-q-and-a|Upstart Q&A UDS session]]
 * [[UbuntuSpec:foundations-m-installer-redesign|
Implement the installer redesign spec]] (EvanDandrea)
 * [[UbuntuSpec:foundations-m-update-notifier-refactor|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)
Line 11: Line 13:
 * [[UbuntuSpec:foundations-m-package-removal-in-upgrade|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).
 * [[UbuntuSpec:foundations-karmic-install-updates-when-installing|Download updates while installing]] (EvanDandrea)
 * [[UbuntuSpec:foundations-m-release-upgrader-dbus-refactor|D-Bus Refactor of release-upgrader]] - discuss refactoring the release-upgrader backend as a dbus service to improve reliability/responsiveness (MichaelVogt)

== 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 Chomium to main
 * HUGE push for Software Center
   1. goal: sell stuff in software center,
   1. goal: figure out how to deliver opportunistic apps via the software center
   1. 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
 * It would really help Desktop if Upstart+Plymouth work stabilized so they could work with it

=== Server ===

The server team has listed their planning by priority; their bullet items below reflect this.

 * Priority 1: Cloud cluster file system (maybe?)
 * 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
 * more ...

=== OEM ===

 * Graphical boot selecter that OEM did will likely want Foundations to maintain
 * OEM might want to create an ISO of WebNow
 * more ...

== 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)
   * Migration to Python 3?
   * Eliminate symlinks for python-[central|support] using PEP 3147?
   * Python 2.7?
   * Freezing (e.g. cx_freeze) critical dist upgrade tools?
Line 13: Line 65:

(Numbers in parentheses indicate to-do/postponed/done.)

Ideas

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 Chomium to main
  • HUGE push for Software Center
    1. goal: sell stuff in software center,
    2. goal: figure out how to deliver opportunistic apps via the software center
    3. 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
  • It would really help Desktop if Upstart+Plymouth work stabilized so they could work with it

Server

The server team has listed their planning by priority; their bullet items below reflect this.

  • Priority 1: Cloud cluster file system (maybe?)
  • 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
  • more ...

OEM

  • Graphical boot selecter that OEM did will likely want Foundations to maintain
  • OEM might want to create an ISO of WebNow

  • more ...

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)
    • Migration to Python 3?
    • Eliminate symlinks for python-[central|support] using PEP 3147?
    • Python 2.7?
    • Freezing (e.g. cx_freeze) critical dist upgrade tools?

Lucid specs not done

(Numbers in parentheses indicate to-do/postponed/done.)

Lucid specs partly done

Lucid specs mostly done

FoundationsTeam/Maverick/Planning (last edited 2010-05-04 14:04:46 by p5B09F55E)