O2 PROGRAMMING PROCEDURES

BACKUPS

• The VSS machine will have RAID in case of a crash/failure of HDD etc. so that we should have maximum security. The code will be uploaded to Acton regularly for builds. Also, once a month you should upload the entire code so we have a full backup there.
• You are all responsible for backups of the data on your own machines (e.g., via DVD)

ANTI-VIRUS

• You are each responsible for your own machines security: you must ALL have anti-virus software running and kept up to date.
• Do not put your computer at risk by installing or downloading data, programs, or web pages that are not secure (i.e. are dangerous).

NORMAL COMPILING

• Our standard build day is Monday, so we will build a version AT LEAST every Monday night.
• Under some circumstances (e.g., close to a release), we will want to build more often than that (e.g., once or even more per day).
• The Build Team will send an e-mail informing of the time of the next build.
• You should communicate with the Build Team to make sure that anything that I have requested is included in that build!

EXTREME COMPILING

• When I am visiting a client or a client is waiting for a critical and urgent update or problem, we MUST make SURE that ONLY the fixes that are DIRECTLY REQUESTED are included in the update (EVEN IF something ELSE is a FIX, it should not be included unless specifically requested: it can solve one problem but cause another!)! You MUST apply changes VERY CAREFULLY! Extreme compiling relies on whoever is building the version to be very careful about what updates are included in the version and communicating with programmers to make sure nothing EXCEPT what I request is included.

OLD VERSION COMPILING

• EVERYONE should REGULARLY make sure that they have COMPILE OLD VERSIONS (e.g., V5) of the code... if you perform this on the FIRST DAY OF EACH MONTH then it is unlikely that you will have to compile everything from scratch again.

It is not acceptable to have to wait for hours for the code to compile in order to make a quick fix of an old version! REPORTING

• At the end of each week, you should send a brief report with TT numbers that were finished during the week to your Head Chef: this will allow the Head Chef to see development progress and control TT tasks. If necessary, the Head Chef can then send his own summary report and include your brief descriptions describing the week of work of your team.
• There will be defined standards of Technical Documentation within the code that everyone must follow.

TESTING

• EVERYONE (testers and developers) must use CURRENT and LATEST (NOT DEMO) FIELDPRO database versions for testing
• Make sure your TT list is always up to date and reflects all work that you have performed and plan to perform!