KnowledgeBase
Differences between revisions 102 and 178 (spanning 76 versions)
|
Size: 13447
Comment: Added triaging requests: Incomplete with|without response
|
← 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(triager)>> = Bug Triager = Goal: Move bugs filed against server related packages to '''Triaged''', '''Invalid''' or '''Won't Fix''' status. The Ubuntu Server team participates in the general bug triaging of server related packages. Our resources are primarily focused on the following tasks (from the most important to the less important): 1. Prioritize [[https://bugs.launchpad.net/ubuntu/+bugs?field.searchtext=&orderby=datecreated&field.status%3Alist=NEW&field.importance%3Alist=UNDECIDED&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=&search=Search|new bugs]] to catch critical bugs. 1. Triage [[https://bugs.launchpad.net/ubuntu/+bugs?field.searchtext=&orderby=-importance&field.status%3Alist=NEW&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&field.status%3Alist=CONFIRMED&field.importance%3Alist=CRITICAL&field.importance%3Alist=HIGH&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=&search=Search|High priority bugs]]. 1. Triage [[https://bugs.edge.launchpad.net/ubuntu/+bugs?field.searchtext=&orderby=-importance&search=Search&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&assignee_option=any&field.assignee=&field.bug_reporter=&field.bug_supervisor=&field.bug_commenter=&field.subscriber=ubuntu-server&field.component-empty-marker=1&field.tag=&field.tags_combinator=ANY&field.status_upstream-empty-marker=1&field.has_cve.used=&field.omit_dupes.used=&field.omit_dupes=on&field.affects_me.used=&field.has_no_package.used=&field.has_patch.used=&field.has_branches.used=&field.has_branches=on&field.has_no_branches.used=&field.has_no_branches=on|Incomplete bugs with response ]]. 1. Triage [[ https://bugs.edge.launchpad.net/ubuntu/+bugs?field.searchtext=&orderby=-importance&search=Search&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&assignee_option=any&field.assignee=&field.bug_reporter=&field.bug_supervisor=&field.bug_commenter=&field.subscriber=ubuntu-server&field.component-empty-marker=1&field.tag=&field.tags_combinator=ANY&field.status_upstream-empty-marker=1&field.has_cve.used=&field.omit_dupes.used=&field.omit_dupes=on&field.affects_me.used=&field.has_no_package.used=&field.has_patch.used=&field.has_branches.used=&field.has_branches=on&field.has_no_branches.used=&field.has_no_branches=on| Incomplete bugs without response ]]. 1. Triage [[https://bugs.launchpad.net/ubuntu/+bugs?field.searchtext=&orderby=-importance&search=Search&field.status%3Alist=NEW&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&field.status%3Alist=CONFIRMED&field.importance%3Alist=MEDIUM&field.importance%3Alist=LOW&field.importance%3Alist=WISHLIST&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=|bugs in packages from server related packages]]. 1. Triage bugs in packages you have an interest in. == Daily bug triaging == A specific member of the server team is responsible for looking at the bugs in a '''New''' state and a '''Undecided''' importance on a daily basis in order to set the ''Importance'' on each bug. This is expected to take less than 15 minutes per day. For each bug on the list (search linked above): 1. the '''importance''' '''must''' be set 1. the status '''should''' be updated 1. any missing information '''should''' be asked to the bug reporter and the bug status set to ''INCOMPLETE'' accordingly. The default meanings of Importances and Statuses are explained at [[Bugs/Importance]] and [[Bugs/Status]]. Make sure you have these pages opened when triaging bugs. Feel free to add your name to the list: || Day || '''Assignee''' || '''Assignee''' || '''Assignee''' || || Sunday || || || || || Monday || zul ||hggdh || || || Tuesday || mathiaz || Daviey || || || Wednesday || ttx || hallyn|| || || Thursday || smoser || zul || || || Friday || kirkland || SpamapS || || || Saturday || || || || == Additional 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. * 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]]. == 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. == Stack package names policy == Integration work on specific server stacks (Mail stack, cluster stack, etc...) sometimes result in specific integration binary packages. In order to provide a coherent user experience, those binary packages should follow the following naming rule: ''stackname''-stack-''function'' As an example, mail stack packages could be named "mail-stack-delivery", "mail-stack-relay"... Decision from [[https://wiki.ubuntu.com/MeetingLogs/Server/20100525|20100525 team meeting]]. = 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 [email protected] }}} == 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. = Stable Release Updates = See [[ServerTeam/SRUPolicy]] for more information about the SRU process followed by the Ubuntu Server team. = 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/. ==== 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. a. Update the Agenda for the next meeting at [[ServerTeam/Meeting]] 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)