KnowledgeBase

Differences between revisions 153 and 154
⇤ ← Revision 153 as of 2016-12-09 13:37:29 →
Size: 9238
Editor: powersj
Comment:
← Revision 154 as of 2017-01-26 18:20:10 → ⇥
Size: 7836
Editor: powersj
Comment: Cleaning up testing section to one page
Deletions are marked like this. Additions are marked like this.
Line 64: Line 64:
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.

=== Verification ===

Most, but sadly not all bigger software projects fortunately have functional tests being part of their build process and if stable enough that is usually enabled in deb packaging.
Furthermore most packages have a [[http://packaging.ubuntu.com/html/auto-pkg-test.html|dep8 test]] associated to guarantee basic verification of more complex tests.
But then for server packages in particular sometimes the required constraints or setup can be too complex for a dep8 test. As we go a long we often develop manual or scripted tests for those. I successful and reasonable they might end up being executed regularly in the [[https://jenkins.ubuntu.com/server/|server regression tests]]. But if not we at least leave the breadcrumbs for the next one needing it at [[ServerTeam/VerificationTests|Verification Tests]]		 For an overview of our test areas and opportunities please see the [[Testing/Server|server testing section]] of the overall Ubuntu [[Testing|testing project]].
Line 85: Line 71:
Line 91: Line 76:
Line 103: Line 87:
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 monthly report is a subpage under [[ServerTeam/ReportingPage]]. It's a summary from the Meeting minutes and the "a Month in the archive" post.

Overview

The knowledge base contains development, test, and operational resources specific to the Ubuntu Server team. If you have any questions, don't hesitate to contact other ServerTeam members.

Bug Triage

Goal: To successfully review every bug filed against Ubuntu Server related packages

A review involves analyzing a bug to determine if the bug is valid and if sufficient information was provided. If the bug is both valid and provided with sufficient information, the bug is marked as triaged and will be worked to closure by a member of the server team. Otherwise, the bug will be responded to and marked as 'Incomplete' for more details, 'Invalid' for not a real bug, or 'Won't Fix'.

Here is the list of recently modified bugs in packages used for triage by the server team.

Here is the backlog query for the server team.

Daily bug triaging

Bug triage is completed for all bugs last updated on a particular day. An assigned member of the server team will look at all bugs that were updated on the previous day. For example, the member with responsibility on Friday will review all the bugs updated on Thursday. For the weekend, the member with responsibility on Monday will review all the bugs updated on Friday, Saturday, and Sunday.

This process is expected to take less than 30 minutes per day. This is not meant to be a full root cause analysis (RCA) investigative time, instead only determining if further attention is warranted and sufficient information has been provided.

Current members of Ubuntu Server bug triage:

  • cpaelzer
  • nacc
  • powersj
  • rbasak

Assignment

Assignment of daily bug triage is completed as an agenda item of the server team's IRC meeting.

Additional resources

Helpful Guides and Definitions:

Developer/Packager resources

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

We are 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

For an overview of our test areas and opportunities please see the server testing section of the overall Ubuntu testing project.

Documentation resources

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

Developer resources

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

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 monthly 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/.

Publishing the minutes

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

  1. Go to MeetingLogs/Server and use the form to create a new entry using the format YYYYMMDD. This will create a new page for you with the ServerTeamMeetingLogTemplate.

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

    2. Copy in the IRC logs from the "Minutes" link at the end of the meeting. This can be found on http://ubottu.com/meetingology/logs/ubuntu-meeting/

    3. Updated the minutes section with a summary of each section. You can template to work from using the IRC minutes you found the IRC logs from. Then fill in each section with your summary.

  2. Update ServerTeam/Header to announce the next meeting date.

  3. Update the Agenda for the next meeting at ServerTeam/Meeting

    1. In particular, remove completed ACTIONS, add new ones
    2. Update the list of Chair/Scribes
      1. move yourself to the back
      2. send an email to the person who will chair next week

  4. Publish the minutes to the ubuntu-devel <ubuntu-devel@lists.ubuntu.com> and ubuntu-server <ubuntu-server@lists.ubuntu.com> mailing lists. Use the subject "Server team meeting minutes: YYYY-MM-DD"

CategoryServerTeam

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