Development - Titanium: Difference between revisions

From EPOD
(Created page with "*Assign the bug to yourself (either through the standard Supimix procedures or from the Log List) *Check out the source code to be changed from Visual SourceSafe. *Make and chang...")
 
No edit summary
Line 4: Line 4:
*When complete, check in your changes with an appropriate comment, initially referencing the log. For example:
*When complete, check in your changes with an appropriate comment, initially referencing the log. For example:
**291925 - Fixed X when Y happens
**291925 - Fixed X when Y happens
*Copy the affected source files to the demo machine, on CALIDUS_DEMO. The folder for the system is <pre>C:\Inetpub\wwwroot\EPOD\ on calidius_demo.</pre>
*Copy the affected source files to the demo machine, on CALIDUS_DEMO. The folder for the system is <pre>C:\Inetpub\wwwroot\EPOD\</pre>
*Update the log to Development Complete status in Supimix (or Fixed status on a log list), ensuring that you enter resolution notes.
*Update the log to Development Complete status in Supimix (or Fixed status on a log list), ensuring that you enter resolution notes.
*Assign the log to a tester, who will then test the functionality and close the log (or reassign to be released in a patch).
*Assign the log to a tester, who will then test the functionality and close the log (or reassign to be released in a patch).

Revision as of 10:40, 7 September 2011

  • Assign the bug to yourself (either through the standard Supimix procedures or from the Log List)
  • Check out the source code to be changed from Visual SourceSafe.
  • Make and changes and test locally.
  • When complete, check in your changes with an appropriate comment, initially referencing the log. For example:
    • 291925 - Fixed X when Y happens
  • Copy the affected source files to the demo machine, on CALIDUS_DEMO. The folder for the system is
    C:\Inetpub\wwwroot\EPOD\
  • Update the log to Development Complete status in Supimix (or Fixed status on a log list), ensuring that you enter resolution notes.
  • Assign the log to a tester, who will then test the functionality and close the log (or reassign to be released in a patch).