Ubuntu Wiki

• Launchpad Entry: foo

• Created:

• Contributors:

• Packages affected:

Summary

Put in place procedures to discover major upstream infrastructure changes early and chart the regression potential inherent in these for our users. Use this information at around Feature Freeze to decide whether to push out the new changes or roll back.

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

We need a better idea of what's coming that will affect our users:

• next UDS cycle, grab an early plenary session
• identify key components
• explore those component's communities to determine what's likely to land soon
• record/collate information and develop testplans
• review at feature freeze for deviations of upcoming features
• integrate in the release cycle at a later milestone a go/no-go point for these features
• if we raise issues, can allocate resources at feature freeze

Information to capture in the table:

• impact
  • installed-by-default vs supported in main vs universe

Hypothetical:

• kernel usb stack replacement
  • risk/benefit assessment|rollback analysis:
    • what applications depend on that stack, and need to move
    • forward/roll back in lockstep
    • what likely breakages will occur, and for what percentage of users

Questions:

• Can we link this to feature freeze or some other point in the
• release process?
  • I.E. require all concerns listed addressed in some form by feature freeze
• At what point in the cycle should we advocate rolling back?
  • alpha 6? beta is too late, alpha 5 may not give the QA team enough time to identify
• What if the QA team recommended no-go and the platform still goes with the feature
  • that's fine, we made the recommendation,
  • release-note, work with upstream to address issues

Any target of an UDS session on development is a likely candidate feature

Proposal: track one component in the karmic cycle?

Steve Langasek believes there ought to be a clear overview of what each team is working on.

Action: restart release meetings next week, focusing on the broad overview of upcoming features

Action: start on information gathering at UDS

• steve to talk to people
• henrik to talk to team leads to announce devs to talk to steve
• QA meeting agenda next week to review collected info and review process

What information to gather

• upstream roadmaps
• devs in ubuntu

Community organization to test packages that are landing large features soon

• PPAs of upstream tip of development

Bug Management possibilities:

• Look for bug volume increase when new upstream version lands

Action: talk to Ara about having testing days that focus on writing testcases

• Review at release meeting post-feature-freeze
• at alpha 6, qa team makes final recommendation as to how things have come along.

CategorySpec