Planning

Differences between revisions 29 and 30
Revision 29 as of 2010-04-21 18:54:54
Size: 5779
Editor: c-71-56-223-2
Comment:
Revision 30 as of 2010-04-21 19:03:00
Size: 5816
Editor: c-71-56-223-2
Comment:
Deletions are marked like this. Additions are marked like this.
Line 35: Line 35:
 * Priority 1: Cloud cluster file system (maybe?)  * Priority 1: Cloud cluster file system (not sure if we'll be needed for this or not)

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 (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
  • 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)