Loading...
 
Skip to main content

History: Quality Team

Preview of version: 21

The Quality Team aims to (especially in the stable branch) to share experience and minimize the risk of introducing regression bugs or bad coding practices.

Although there is currently no formal code review process for commits, it is currently being done by the Developers on an ongoing basis through the monitoring of the SVN mailing list. A formal code review process has been implemented before but only for commits in the LTS branches, in the form of a Quality Team. This was abandoned when the amount of overhead became unsustainable. There has been talk about getting some kind of code review process up again, but details are uncertain - in order to have a process that works smoothly and does not depend on too small a group of developers. The plan is to wait till after we've switched to GIT from SVN as that would address a number of issues we faced before including merging issues between the various SVN branches. GIT is also a much better tool via "pull requests" to implement a more distributed code review process. See Distributed revision control.

Release responsibilities

Ongoing responsibilities

Task

Projects


More details: dev:Quality Team

Aliases

History

Advanced
Information Version
Marc Laporte 29
View
Marc Laporte I deleted team since it won't come back 28
View
Marc Laporte 27
View
Marc Laporte 26
View
Marc Laporte 25
View
Marc Laporte 24
View
Marc Laporte 23
View
Marc Laporte 22
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. 21
View
Nelson Ko 20
View
Nelson Ko 19
View
Nelson Ko 18
View
Nelson Ko 17
View
Nelson Ko 16
View
Marc Laporte 15
View
Marc Laporte 14
View
Marc Laporte Cleanup 13
View
Marc Laporte 12
View
Marc Laporte Thank you! 11
View
Marc Laporte 10
View
Frank Guthausen link clickable 9
View
Marc Laporte 8
View
Marc Laporte 7
View
Marc Laporte 4
View
Marc Laporte 3
View
  • «
  • 1 (current)
  • 2