KnowledgeBase
Differences between revisions 87 and 178 (spanning 91 versions)
|
Size: 14929
Comment:
|
← Revision 178 as of 2019-12-10 22:29:10 ⇥
Size: 16
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| <<Include(ServerTeam/Header)>> ||<tablestyle="float:right; font-size: 0.9em; width:40%; background:#F1F1ED; margin: 0 0 1em 1em;" style="padding:0.5em;"><<TableOfContents(1)>>|| Here are some ressources to help you get things done. If you have any questions, don't hesitate to [[ServerTeam/Contact|contact]] other ServerTeam members. <<Anchor(triagger)>> = 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 [[https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad|ubuntu-bugsquad mailing list]] and #ubuntu-bugs on irc.freenode.org. * The launchpad [[http://launchpad.net/people/ubuntu-server|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. * [[https://bugs.launchpad.net/~ubuntu-server/+packagebugs|summary report of bugs by package]]. * 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''' || || [[http://qa.ubuntu.com/reports/ubuntu-server-team/dailynewbugs.ubuntu-server.sun.html|Sunday bug list]] || zul (on Monday) || || || || [[http://qa.ubuntu.com/reports/ubuntu-server-team/dailynewbugs.ubuntu-server.mon.html|Monday bug list]] || soren (on Tuesday) || || || || [[http://qa.ubuntu.com/reports/ubuntu-server-team/dailynewbugs.ubuntu-server.tue.html|Tuesday bug list]] || ttx (on Wednesday) || || || || [[http://qa.ubuntu.com/reports/ubuntu-server-team/dailynewbugs.ubuntu-server.wed.html|Wednesday bug list]] || smoser (on Thursday) || || || || [[http://qa.ubuntu.com/reports/ubuntu-server-team/dailynewbugs.ubuntu-server.thu.html|Thursday bug list]] || kirkland (on Friday) || || || || [[http://qa.ubuntu.com/reports/ubuntu-server-team/dailynewbugs.ubuntu-server.fri.html|Friday bug list]] || mathiaz (on Monday) || || || || [[http://qa.ubuntu.com/reports/ubuntu-server-team/dailynewbugs.ubuntu-server.sat.html|Saturday bug list]] || zul (on Monday) || || || * Then the [[http://tinyurl.com/untriaged-ubuntu-server|Non-triaged Ubuntu Server bugs]] list presents, by priority, where the triaging effort should be directed. == 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 [[MOTU|MOTUs, the Master Of The Universe]]. * There is the [[PackagingGuide]]. * [[PackagingGuide/Lists/DocumentationResources]] and [[MOTU/School]] have information related to packaging. * [[UbuntuDevelopers]] explains how to become an official packager. * [[https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu|ubuntu-motu mailing list]] and #ubuntu-motu on irc.freenode.org are good places to ask for help. We're focusing on server related packages in main and universe. * Developers can use the [[http://tinyurl.com/triaged-ubuntu-server|Triaged Ubuntu Server bugs]] list to prioritize their work. = Server support resources = The server team offers support for server-related questions in #ubuntu-server. * The [[https://wiki.ubuntu.com/UbuntuBots|ubottu]] irc bot makes it easy to share an extensive set of [[http://ubottu.com/factoids.cgi|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 [[https://wiki.ubuntu.com/UbuntuBots|ubottu]] for more details. = Tester resources = We coordinate our testing plans in the [[Testing/Server|Server testing section]] of the [[Testing|Testing project]]. New test plans should be defined as new pages below [[Testing/Server]]. Example: Testing/Server/My''''''Test''''''Plan. === ISO testing === Ubuntu Server iso testing follows the process described in [[Testing/ISO]]. We focus on testing the ubuntu-server isos following the [[Testing/Cases/ServerInstall|Server installation test cases]]. The [[http://iso.qa.ubuntu.com/|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 [[http://doc.ubuntu.com/ubuntu/serverguide/C/index.html|Ubuntu Server Guide]] and the [[https://help.ubuntu.com/community/|community help website]]. We're working with the DocumentationTeam and focus on server related topics. <<Anchor(serverguide)>> == Ubuntu Server Guide == The current development version of the Ubuntu Server Guide is located in [[https://code.launchpad.net/~ubuntu-core-doc/ubuntu-doc/ubuntu-intrepid|a bazaar branch]] (lp:ubuntu-doc) hosted on Launchpad. There is also [[http://doc.ubuntu.com/ubuntu/serverguide/C/index.html|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 [[https://help.ubuntu.com/community/WikiGuide|WikiGuide]] has guidelines for contributing to the help website. * If help is needed, the [[http://lists.ubuntu.com/mailman/listinfo/ubuntu-doc|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 [[https://wiki.ubuntu.com/|Ubuntu Team wiki]] is the central location where Ubuntu developers exchange ideas and track their progress. * UbuntuDevelopment gives an overview of the development processes. * The [[http://lists.ubuntu.com/mailman/listinfo/ubuntu-devel|ubuntu-devel mailing list]] and #ubuntu-devel on irc.freenode.net are the places where ubuntu developers can be found. = 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 1. 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 [[https://code.launchpad.net/~mathiaz/+junk/multi-package-bugs-fixed/|multi-package-bugs-fixed script]]. * Criteria for acceptation are described in the "When" part of the [[StableReleaseUpdates#When|Stable release updates policy]] * Candidates are accepted or declined and make it to the accepted candidates list 1. SRU preparation * Anyone can assign himself to one of those accepted SRU candidates and produce the required elements * Assignee should provide: * A SRU report (see [[StableReleaseUpdates#Procedure|step 2 of the SRU procedure]]) * A branch merge proposal, and assign ubuntu-server to the merge review 1. 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: * [[https://bugs.launchpad.net/ubuntu/karmic/+bugs?field.tag=uec|Karmic SRU bugs for UEC]] = Team policy = === Membership === The Membership policy is described in [[ServerTeam/Membership|Membership]]. === Reporting === The ServerTeam has a section in the [[TeamReports| monthly report]]. We try to get status reports on a weekly basis on the day preceding the IRC meeting. The [[ServerTeam/ReportingPage| 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 [[TeamReports| 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 [[ServerTeam/Meeting| Meeting]] page presents the Agenda for the next meeting. [[ScribesTeam/MootBot|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. 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. [[http://qa.ubuntu.com/reports/ubuntu-server-team/fixedbugs.ubuntu-server.latest.html|list of bugs fixed in the last 8 days]] 1. Review the [[http://qa.ubuntu.com/reports/ubuntu-server-team/acceptedbugs.ubuntu-server.latest.html|accepted list]]: a. status on bugs that have a person assigned. a. purge bugs that are related to an unmaintained release. 1. Review [[https://code.launchpad.net/~ubuntu-server/+activereviews|SRU branch proposal]]: a. status on branches that have a person assigned. a. 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]]. a. Move the agenda from [[ServerTeam/Meeting]] to agenda section. a. Copy the irc logs to the Irc log section. a. Update [[ServerTeam/Header]] to announce the next meeting date. a. Write the minutes. 1. Publish the minutes: * on ubuntu-server and ubuntu-devel mailing lists * on the [[http://ubuntuserver.wordpress.com|ubuntuserver blog]] (or another blog syndicated on [[http://planet.ubuntu.com/|Planet Ubuntu]]). [[http://bazaar.launchpad.net/~mathiaz/+junk/ubuntuserver-minutes/files|A script]] has been written to automate this step. ---- CategoryServerTeam |
See ServerTeam |
See ServerTeam
ServerTeam/KnowledgeBase (last edited 2019-12-10 22:29:10 by powersj)