KnowledgeBase

Differences between revisions 87 and 88
Revision 87 as of 2009-12-23 18:45:13
Size: 14929
Editor: bar67-1-82-227-44-92
Comment:
Revision 88 as of 2010-02-22 18:52:16
Size: 14884
Editor: dsl-173-206-1-210
Comment:
Deletions are marked like this. Additions are marked like this.
Line 165: Line 165:
    a. [[https://bugs.launchpad.net/ubuntu/dapper/+nominations?field.searchtext=&orderby=-importance&field.status%3Alist=FIXRELEASED&assignee_option=any&field.assignee=&field.bug_reporter=&field.bug_supervisor=ubuntu-server&field.bug_commenter=&field.subscriber=&field.component-empty-marker=1&field.status_upstream-empty-marker=1&field.omit_dupes.used=&field.omit_dupes=on&field.has_patch.used=&field.has_cve.used=&field.tag=&field.tags_combinator=ANY&field.has_no_package.used=&search=Search|list of nominated bugs for dapper]]
    a. [[https://bugs.launchpad.net/ubuntu/hardy/+nominations?field.searchtext=&orderby=-importance&field.status%3Alist=FIXRELEASED&assignee_option=any&field.assignee=&field.bug_reporter=&field.bug_supervisor=ubuntu-server&field.bug_commenter=&field.subscriber=&field.component-empty-marker=1&field.status_upstream-empty-marker=1&field.omit_dupes.used=&field.omit_dupes=on&field.has_patch.used=&field.has_cve.used=&field.tag=&field.tags_combinator=ANY&field.has_no_package.used=&search=Search|list of nominated bugs for hardy]]
    a. [[https://bugs.launchpad.net/ubuntu/intrepid/+nominations?field.searchtext=&orderby=-importance&field.status%3Alist=FIXRELEASED&assignee_option=any&field.assignee=&field.bug_reporter=&field.bug_supervisor=ubuntu-server&field.bug_commenter=&field.subscriber=&field.component-empty-marker=1&field.status_upstream-empty-marker=1&field.omit_dupes.used=&field.omit_dupes=on&field.has_patch.used=&field.has_cve.used=&field.tag=&field.tags_combinator=ANY&field.has_no_package.used=&search=Search|list of nominated bugs for intrepid]]
    a. [[https://bugs.launchpad.net/ubuntu/jaunty/+nominations?field.searchtext=&orderby=-importance&field.status%3Alist=FIXRELEASED&assignee_option=any&field.assignee=&field.bug_reporter=&field.bug_supervisor=ubuntu-server&field.bug_commenter=&field.subscriber=&field.component-empty-marker=1&field.status_upstream-empty-marker=1&field.omit_dupes.used=&field.omit_dupes=on&field.has_patch.used=&field.has_cve.used=&field.tag=&field.tags_combinator=ANY&field.has_no_package.used=&search=Search|list of nominated bugs for jaunty]]
    a. [[https://bugs.launchpad.net/ubuntu/karmic/+nominations?field.searchtext=&orderby=-importance&field.status%3Alist=FIXRELEASED&assignee_option=any&field.assignee=&field.bug_reporter=&field.bug_supervisor=ubuntu-server&field.bug_commenter=&field.subscriber=&field.component-empty-marker=1&field.status_upstream-empty-marker=1&field.omit_dupes.used=&field.omit_dupes=on&field.has_patch.used=&field.has_cve.used=&field.tag=&field.tags_combinator=ANY&field.has_no_package.used=&search=Search|list of nominated bugs for karmic]]
    a. [[https://bugs.launchpad.net/ubuntu/dapper/+nominations?field.searchtext=&orderby=-importance&search=Search&assignee_option=any&field.assignee=&field.bug_reporter=&field.bug_supervisor=ubuntu-server&field.bug_commenter=&field.subscriber=&field.component-empty-marker=1&field.status_upstream-empty-marker=1&field.omit_dupes.used=&field.omit_dupes=on&field.has_patch.used=&field.has_cve.used=&field.affects_me.used=&field.tag=&field.tags_combinator=ANY&field.has_no_package.used=|list of nominated bugs for dapper]]
    a. [[https://bugs.launchpad.net/ubuntu/hardy/+nominations?field.searchtext=&orderby=-importance&search=Search&assignee_option=any&field.assignee=&field.bug_reporter=&field.bug_supervisor=ubuntu-server&field.bug_commenter=&field.subscriber=&field.component-empty-marker=1&field.status_upstream-empty-marker=1&field.omit_dupes.used=&field.omit_dupes=on&field.has_patch.used=&field.has_cve.used=&field.affects_me.used=&field.tag=&field.tags_combinator=ANY&field.has_no_package.used=|list of nominated bugs for hardy]]
    a. [[https://bugs.launchpad.net/ubuntu/intrepid/+nominations?field.searchtext=&orderby=-importance&search=Search&assignee_option=any&field.assignee=&field.bug_reporter=&field.bug_supervisor=ubuntu-server&field.bug_commenter=&field.subscriber=&field.component-empty-marker=1&field.status_upstream-empty-marker=1&field.omit_dupes.used=&field.omit_dupes=on&field.has_patch.used=&field.has_cve.used=&field.affects_me.used=&field.tag=&field.tags_combinator=ANY&field.has_no_package.used=|list of nominated bugs for intrepid]]
    a. [[https://bugs.launchpad.net/ubuntu/jaunty/+nominations?field.searchtext=&orderby=-importance&search=Search&assignee_option=any&field.assignee=&field.bug_reporter=&field.bug_supervisor=ubuntu-server&field.bug_commenter=&field.subscriber=&field.component-empty-marker=1&field.status_upstream-empty-marker=1&field.omit_dupes.used=&field.omit_dupes=on&field.has_patch.used=&field.has_cve.used=&field.affects_me.used=&field.tag=&field.tags_combinator=ANY&field.has_no_package.used=|list of nominated bugs for jaunty]]
    a. [[https://bugs.launchpad.net/ubuntu/karmic/+nominations?field.searchtext=&orderby=-importance&search=Search&assignee_option=any&field.assignee=&field.bug_reporter=&field.bug_supervisor=ubuntu-server&field.bug_commenter=&field.subscriber=&field.component-empty-marker=1&field.status_upstream-empty-marker=1&field.omit_dupes.used=&field.omit_dupes=on&field.has_patch.used=&field.has_cve.used=&field.affects_me.used=&field.tag=&field.tags_combinator=ANY&field.has_no_package.used=|list of nominated bugs for karmic]]

Here are some ressources to help you get things done.

If you have any questions, don't hesitate to contact other ServerTeam members.

Bug Triager resources

Triaging bugs in Launchpad is coordinated with the BugSquad team:

  • BugSquad/KnowledgeBase has valuable information on how to work with bugs in Launchpad.

  • Bugs/Responses has a list of standard responses for different categories of bugs.

  • Ask for help on the ubuntu-bugsquad mailing list and #ubuntu-bugs on irc.freenode.org.

  • The launchpad ubuntu-server team is the bug contact for many server-related packages, so if you become a member of the team you'll get email traffic related to those bugs. Avoid assigning or subscribing ubuntu-server for packages ubuntu-server is already a bug contact for.

  • Daily New,Undecided bug lists: each list should be reviewed on the relevant day of the week. All bugs on the list should be looked at and have their importance set (as well as their status updated if possible). Feel free to add your name to the list:

Bug list to review

Assignee

Assignee

Assignee

Sunday bug list

zul (on Monday)

Monday bug list

soren (on Tuesday)

Tuesday bug list

ttx (on Wednesday)

Wednesday bug list

smoser (on Thursday)

Thursday bug list

kirkland (on Friday)

Friday bug list

mathiaz (on Monday)

Saturday bug list

zul (on Monday)

Official tags

The following tags are used by the server team to track bugs relevant to various components:

  • uec: bugs related to UEC, the platform.
  • uec-images: bugs related to the images (guests) running on UEC.
  • ec2-images: bugs related to the images (AMIs) running on EC2.
  • eucalyptus: bugs related to eucalyptus the platform and shared with the upstream developers.

Developer/Packager resources

For packaging information, head to the MOTUs, the Master Of The Universe.

We're focusing on server related packages in main and universe.

Server support resources

The server team offers support for server-related questions in #ubuntu-server.

  • The ubottu irc bot makes it easy to share an extensive set of factoids to others in an irc channel. E.g. typing !ask | noobie will cause ubottu to tell noobie that folks should just go ahead and ask their questions. Ubottu can also conveniently show the channel information on bugs and packages. See ubottu for more details.

Tester resources

We coordinate our testing plans in the Server testing section of the Testing project.

New test plans should be defined as new pages below Testing/Server. Example: Testing/Server/MyTestPlan.

ISO testing

Ubuntu Server iso testing follows the process described in Testing/ISO. We focus on testing the ubuntu-server isos following the Server installation test cases. The Iso testing tracker is used to track test results.

You can register with the iso testing tracker and subscribe to the ubuntu server testcases so that you'll be notified whenever a new ubuntu-server iso needs to be tested.

Documentor resources

This area is involved with updating and creating new content for the Ubuntu Server Guide and the community help website. We're working with the DocumentationTeam and focus on server related topics.

Ubuntu Server Guide

The current development version of the Ubuntu Server Guide is located in a bazaar branch (lp:ubuntu-doc) hosted on Launchpad. There is also an html version available online.

Here are the steps to modify the Ubuntu Server Guide and ask the DocumentationTeam to review your changes:

  • Create a directory where you'll put your local working version of the Ubuntu Server Guide:

$ bzr init-repo --trees --format=dirstate-with-subtree ubuntu-bzr
$ cd ubuntu-doc/
  • Get the ubuntu-docs files that have the latest version of the Ubuntu Server Guide:

$ bzr branch lp:ubuntu-docs
$ cd ubuntu-doc/

NB: that command can take some time as the whole history of the branch has to be downloaded from Launchpad.

  • Update the Ubuntu Server Guide files using your favorite editor. They can be found in the serverguide/C/ directory.

  • Once your changes are complete, commit them:

$ bzr ci

And send them to the ubuntu-doc mailing lists with the bzr send command:

$ bzr send --mail-to=ubuntu-doc@lists.ubuntu.com

Community wiki

  • The WikiGuide has guidelines for contributing to the help website.

  • If help is needed, the ubuntu-doc mailing list and #ubuntu-doc on irc.freenode.net are good places to ask around.

The Ubuntu Team wiki, at https://wiki.ubuntu.com/, is focused on documentation for Ubuntu community contributors rather than for end users

Developer resources

The Ubuntu Team wiki is the central location where Ubuntu developers exchange ideas and track their progress.

SRU resources

Stable Release Updates (SRU) are updates fixing bugs in stable supported releases. The Ubuntu Server team follows the following process to track potential SRU candidates and transform them into proposed updates:

  1. Candidates collection
    • Bugs get fixed in the development release
    • Bugs get nominated for a given release by the community as a wanted bugfix update
  2. Candidates review
    • During the weekly Server team meeting we review the list of server bugs fixed in the development release in the last week and the list of server bugs nominated for supported releases. The list of bugs fixed in the development release can be generated with the multi-package-bugs-fixed script.

    • Criteria for acceptation are described in the "When" part of the Stable release updates policy

    • Candidates are accepted or declined and make it to the accepted candidates list
  3. SRU preparation
    • Anyone can assign himself to one of those accepted SRU candidates and produce the required elements
    • Assignee should provide:
  4. SRU review/sponsoring/upload
    • Server team MOTUs or core-devs look at the list of accepted server SRU candidates with a branch merge proposed and assign themselves to the merge proposal review
    • Reviewer checks that a proper SRU report is provided, reviews the branch merge proposal, and either
      • Rejects the branch merge proposal
      • Accepts it, uploads the package to -proposed, subscribes the relevant SRU team to it, marks branch as merged
    • Reviewer and assignee should not be the same person.

Component targeted lists for SRU

Some components (spanning multiple packages) have specific lists of bugs to be tracked:

Team policy

Membership

The Membership policy is described in Membership.

Reporting

The ServerTeam has a section in the monthly report. We try to get status reports on a weekly basis on the day preceding the IRC meeting. The ReportingPage is used to gather the outcome of the tasks done by the ServerTeam members during the week.

The montly report is a subpage under ServerTeam/ReportingPage. It's a summary from the Meeting minutes and the "a Month in the archive" post.

The subpage is automatically included in the monthly team report with a macro as defined in the ServerTeam wiki page.

IRC meeting

We hold IRC meeting regularly to report about current tasks and define new ones. The Meeting page presents the Agenda for the next meeting.

MootBot can be used to record the meeting.

irclogs are available on http://irclogs.ubuntu.com/.

SRU weekly review

  1. Review nominated list and last week fix released bugs to either accept them or mark them won't fix.
    1. list of nominated bugs for dapper

    2. list of nominated bugs for hardy

    3. list of nominated bugs for intrepid

    4. list of nominated bugs for jaunty

    5. list of nominated bugs for karmic

    6. list of bugs fixed in the last 8 days

  2. Review the accepted list:

    1. status on bugs that have a person assigned.
    2. purge bugs that are related to an unmaintained release.
  3. Review SRU branch proposal:

    1. status on branches that have a person assigned.
    2. assign person for review.

Publishing the minutes

Once the meeting is over, minutes are prepared to summarized the outcome of the meeting.

  1. Create a new entry in MeetingLogs/Server/YYYYMMDD with the ServerTeamMeetingLogTemplate.

    1. Move the agenda from ServerTeam/Meeting to agenda section.

    2. Copy the irc logs to the Irc log section.
    3. Update ServerTeam/Header to announce the next meeting date.

    4. Write the minutes.
  2. Publish the minutes:

    A script has been written to automate this step.


CategoryServerTeam

ServerTeam/KnowledgeBase (last edited 2019-12-10 22:29:10 by powersj)