Python2.6ForHardy

  • Launchpad Entry: foundations-karmic-python2.5

  • Created:

  • Contributors: Barry Warsaw, Elliot Murphy, Steve Langasek, Scott Kitterman, Matthias Klose, and James Troup

  • Packages affected: python

Summary

Developing for Hardy currently requires Python 2.5. We want to discuss the best way to support these users for Karmic, which currently only has Python2.6.

Release Note

This section should include a paragraph describing the end-user impact of this change. It is meant to be included in the release notes of the first release in which it is implemented. (Not all of these will actually be included in the release notes, at the release manager's discretion; but writing them is a useful exercise.)

It is mandatory.

Rationale

This should cover the _why_: why is this change being proposed, what justifies it, where we see this justified.

User stories

Assumptions

Design

You can have subsections that better describe specific parts of the issue.

Implementation

This section should describe a plan of action (the "how") to implement the changes discussed. Could include subsections like:

UI Changes

Should cover changes required to the UI, or specific UI that is required to implement this

Code Changes

Code changes should include an overview of what needs to change, and in some cases even the specific details.

Migration

Include:

  • data migration, if any
  • redirects from old URLs to new ones, if any
  • how users will be pointed to the new way of doing things, if necessary.

Test/Demo Plan

It's important that we are able to test new features, and demonstrate them to users. Use this section to describe a short plan that anybody can follow that demonstrates the feature is working. This can then be used during testing, and to show off after release. Please add an entry to http://testcases.qa.ubuntu.com/Coverage/NewFeatures for tracking test coverage.

This need not be added or completed until the specification is nearing beta.

Unresolved issues

This should highlight any issues that should be addressed in further specifications, and not problems with the specification itself; since any specification with problems cannot be approved.

BoF agenda and discussion

Proposed Solution

Create a Hardy Python 2.6 LP Team and PPA

  • include modules for Launchpad, Landscape, and Online Services
  • packages named python-2.6-XXX
  • allow other parties to create their own dependent PPAs for their needs
  • upload rights to this PPA is restricted to core-dev
  • we will drop Python 2.5 from Karmic


CategorySpec

FoundationsTeam/Specs/Python2.6ForHardy (last edited 2009-05-26 14:18:51 by 80)