Development Code Reviews - Revision history

Anw: Update for new network folder structures.

2019-10-04T16:34:04Z

Update for new network folder structures.

Anw at 10:44, 27 March 2015

2015-03-27T10:44:53Z

← Older revision		Revision as of 12:44, 27 March 2015
Line 21:		Line 21:

	If any changes are deferred and/or raised as another Supimix log for completion, the QC folder for this change will be moved to the following directory: P:\EPOD\_Development\QC Documents\Prog QC\# Deferred (Passed)\.		If any changes are deferred and/or raised as another Supimix log for completion, the QC folder for this change will be moved to the following directory: P:\EPOD\_Development\QC Documents\Prog QC\# Deferred (Passed)\.

			[[Category:WI 287575 EPOD Development and Release Process\|150]]

Anw: Created page with "=== Development QC Process === Code reviews are in place for the EPOD projects and must be followed. The Supimix log must be referred to the Product Development Manager for assi..."

2015-03-27T10:42:40Z

Created page with "=== Development QC Process === Code reviews are in place for the EPOD projects and must be followed. The Supimix log must be referred to the Product Development Manager for assi..."

New page

=== Development QC Process ===
Code reviews are in place for the EPOD projects and must be followed.

The Supimix log must be referred to the Product Development Manager for assignation to a peer for review.

When assigned, the development will be reviewed for:
* Technical issues
* Adherence to standards in:
** Modified Code
** Existing Code (may be deferred)

A QC Document will be created for each module modified as part of this change, in the format as per the example P:\EPOD\Procedure\EPOD .Net Development Guide & Process\Dev QC document example\312147 - Lanemark QC.doc.

QC review documents with any outstanding issues will be placed in an appropriately-named folder within the following folder: P:\EPOD\_Development\QC Documents\Prog QC\.

For example: P:\EPOD\_Development\QC Documents\Prog QC\324491 - Use auto-update to refresh load data for existing load

Any issues with code should be passed back to the developer, referencing the QC documents created. Any further changes will be reviewed again following this process.

If all code passes QC review at any time, the QC folder for this change will be moved to the following directory: P:\EPOD\_Development\QC Documents\Prog QC\# Closed\.

If any changes are deferred and/or raised as another Supimix log for completion, the QC folder for this change will be moved to the following directory: P:\EPOD\_Development\QC Documents\Prog QC\# Deferred (Passed)\.

← Older revision		Revision as of 18:34, 4 October 2019
Line 1:		Line 1:
	=== Development QC Process ===		=== Development QC Process ===
	Code reviews are in place for the EPOD projects and must be followed.		Code reviews are in place for the EPOD projects and must be followed.

			{{Warning}} The following is the old process. The new process requires the use of TFS and is documented separately.

	The Supimix log must be referred to the Product Development Manager for assignation to a peer for review.		The Supimix log must be referred to the Product Development Manager for assignation to a peer for review.
Line 10:		Line 12:
	** Existing Code (may be deferred)		** Existing Code (may be deferred)

	A QC Document will be created for each module modified as part of this change, in the format as per the example P:\EPOD\Procedure\EPOD .Net Development Guide & Process\Dev QC document example\312147 - Lanemark QC.doc.		A QC Document will be created for each module modified as part of this change, in the format as per the example P:\Product\EPOD\Procedure\EPOD .Net Development Guide & Process\Dev QC document example\312147 - Lanemark QC.doc.

	QC review documents with any outstanding issues will be placed in an appropriately-named folder within the following folder: P:\EPOD\_Development\QC Documents\Prog QC\.		QC review documents with any outstanding issues will be placed in an appropriately-named folder within the following folder: P:\Product\EPOD\_Development\QC Documents\Prog QC\.

	For example: P:\EPOD\_Development\QC Documents\Prog QC\324491 - Use auto-update to refresh load data for existing load		For example: P:\Product\EPOD\_Development\QC Documents\Prog QC\324491 - Use auto-update to refresh load data for existing load

	Any issues with code should be passed back to the developer, referencing the QC documents created. Any further changes will be reviewed again following this process.		Any issues with code should be passed back to the developer, referencing the QC documents created. Any further changes will be reviewed again following this process.

	If all code passes QC review at any time, the QC folder for this change will be moved to the following directory: P:\EPOD\_Development\QC Documents\Prog QC\# Closed\.		If all code passes QC review at any time, the QC folder for this change will be moved to the following directory: P:\Product\EPOD\_Development\QC Documents\Prog QC\# Closed\.

	If any changes are deferred and/or raised as another Supimix log for completion, the QC folder for this change will be moved to the following directory: P:\EPOD\_Development\QC Documents\Prog QC\# Deferred (Passed)\.		If any changes are deferred and/or raised as another Supimix log for completion, the QC folder for this change will be moved to the following directory: P:\Product\EPOD\_Development\QC Documents\Prog QC\# Deferred (Passed)\.

	[[Category:WI 287575 EPOD Development and Release Process\|150]]		[[Category:WI 287575 EPOD Development and Release Process\|150]]