MeetingReports

Differences between revisions 2 and 3
Revision 2 as of 2012-04-12 22:16:41
Size: 4122
Editor: effenberg0x0
Comment:
Revision 3 as of 2012-04-12 22:24:57
Size: 4186
Editor: effenberg0x0
Comment:
Deletions are marked like this. Additions are marked like this.
Line 3: Line 3:
= Agenda =
== Apr. 18 2012 ==
= Agenda and Previous Meetings Reports =
== Next Meeting ==
=
== Apr. 18th 2012 ===
Line 6: Line 7:
~-Add your suggestion drectly to the bullets below. Please add the ``@SIG``@``macro at the end of the line. When you '''save''' the page, your name/timestamp will be automatically added.-~
 * Check if groups of selected testers (Cariboo907)has accepted to participate.-- [[LaunchpadHome:effenberg0x0]] <<DateTime(2012-04-12T22:16:41Z)>>
~-Add your suggestion drectly to the bullets below. Please use the ``@SIG``@`` macro at the end of the line. When you '''save''' the page, your name/timestamp will be automatically added.-~
 * Check if groups of selected testers (Cariboo907) has accepted to participate.-- [[LaunchpadHome:effenberg0x0]] <<DateTime(2012-04-12T22:16:41Z)>>
Line 13: Line 14:
= Previous Meetings =
== Apr. 12 2012 ==
== Previous Meetings ==
=== Apr. 12th 2012 ===
Line 18: Line 19:
== Apr. 4th. 2012 (kickoff) == === Apr. 4th. 2012 (kickoff) ===
Line 28: Line 29:
= Other suggested topics = = Other Suggested Topics =

About
IconsPage/picto_articles_48.png

Home
About the Project

DocsIconsPage/picto_articles_48.png

Project Specifications
Meeting Reports, ToDo and Agenda

Live TestingIconsPage/picto_articles_48.png

Sessions Schedule
Sessions Reports

ContactIconsPage/picto_articles_48.png

Contact the Team

Click here to access full instructions for the current Live Testing Session.

Agenda and Previous Meetings Reports

Next Meeting

Apr. 18th 2012

Suggested Topics:
Add your suggestion drectly to the bullets below. Please use the @SIG@ macro at the end of the line. When you save the page, your name/timestamp will be automatically added.

  • Check if groups of selected testers (Cariboo907) has accepted to participate.-- effenberg0x0 2012-04-12 22:16:41

  • Check and discuss list of target Packages/Bugs sent by team members during the week. Define final list.
  • Confirm who will approach developers for the selected targets (Balloons?) and if help from other member is needed for this task.-- effenberg0x0 2012-04-12 22:16:41

  • Decide who will be responsible for creating LiveTesting Page, which contains all the info for the testing session.-- effenberg0x0 2012-04-12 22:16:41

  • Decide who will approach IRC Management and get us infrastructure (and, also, if that will be needed in the trial).-- effenberg0x0 2012-04-12 22:16:41

  • ToDo: Wait for feedback from developers. Once a developers accepts to take part in the trial, we can proceed to creating the documentation and setting up a date.-- effenberg0x0 2012-04-12 22:16:41

Previous Meetings

Apr. 12th 2012

  • Cariboo907 has selected a group of testers and will approach them. He will communicate us of the status of this process in the next meeting.-- effenberg0x0 2012-04-12 22:16:41

  • The group agreed to study and select potential target Packages/Bugs throughout next 7 days so that we a list to evaluate in the next meeting.-- effenberg0x0 2012-04-12 22:16:41

  • Once a list of potential target Packages/Bugs is defined, Balloons agreed to reach for developers.-- effenberg0x0 2012-04-12 22:16:41

Apr. 4th. 2012 (kickoff)

References:

Other Suggested Topics

  • Discuss previous attempts, linked at the topic "Ubuntu Previous Attempts" in this document (see index). They were completely unknown to me. Why did they fail? What can we learn from them? -- effenberg0x0 2012-04-05 06:59:22

  • Infrastructure: A more "in-depth" look at Fedora's implementation revealed to me some infrastructure we currently do not have: Special repos for Live Testing ISOs, Testing Builds of packages updated during the session, a tracker updated in real time during the session, with testing results of session participants, a system to host each tester hardware profile (relevant for developers to evaluate each test result vs hardware tested). -- effenberg0x0 2012-04-05 06:59:22

LiveTesting/MeetingReports (last edited 2012-04-12 22:24:57 by effenberg0x0)