Loading...
 

History: Continuous Integration Team

Preview of version: 18



See also: Testing

Release responsibilities


Ongoing

Project

Questions

  • I think we should split this further into 2 sub teams. One which focuses on automation, and the other on great test plans and a team of testers. This second team should work more closely with the Configuration Profiles Team.

Related links

Aliases

Testing

History

Advanced
Information Version
Gary Cunningham-Lee Added inactive members note. 25
View
Marc Laporte Moving non-automated testing to relevant team 24
View
Marc Laporte show.tiki.org is running and not related to CI 23
View
Marc Laporte 22
View
Marc Laporte Old Testing Team becomes Continuous Integration Team, and manual testing becomes the responsibility of the Wishlist Triage team (since they see all the reported bugs, they know what to test) 21
View
Marc Laporte 20
View
Marc Laporte 19
View
Marc Laporte 18
View
Marc Laporte Undo the change from "Testing Team" to "Testing". We need teams of people that take responsibility and do stuff. Some teams will 0 or 1 members and it's our job to find doers and make it happen. 17
View
Marc Laporte Nelson had removed this section, which makes no sense. The point of a team is to have members who get things done. 16
View
Nelson Ko 15
View
Nelson Ko 14
View
Marc Laporte 13
View
Marc Laporte 12
View
Marc Laporte 11
View
Marc Laporte 10
View
Marc Laporte 9
View
Marc Laporte 8
View
Marc Laporte 7
View
Marc Laporte 6
View
Marc Laporte 5
View
Marc Laporte 4
View
Marc Laporte 1
View