ATdeveloper

Check list for installer

1. Misc Folder:

• CGHTools
• R installer
• Rserve
• Java installer
• Microsoft C++ 2010 SP1 Redistribute packages, vcredist_x64.exe & vcredist_x86.exe

1. License file

C:\Installer-2012\ArrayTools-Scripts\V4_3_And_CGH_1_3_RServe_Full\Setup Files\Compressed Files\Language Independent\OS Independent\License.doc. It is a text file.

1. License file

C:\Installer-2012\CGHTools-Scripts\CGH_1_3_Rserve\Setup Files\Compressed Files\Language Independent\OS Independent\License.doc. It is a text file.

1. License agreement menu, About ArrayTools and About CGHTools

menus.

1. Sample datasets.
2. ArrayTools: License.doc, Readme.doc.
3. ArrayTools\Updates: ArrayTools_CurrentVersion.txt.
4. ArrayTools\Doc: Manual.doc, ManualFrame.doc, Overview of

Analysis Tools.doc, Plug-in Manual.doc, StatMethods.doc, Table of Contents.doc, FAQs.pdf.

1. CGHTools: LICENSE AGREEMENT.doc, Readme.doc
2. CGHTools\Updates: CGHTools_CurrentVersion.txt.
3. CGHTools\Doc: CGHManual.doc, CGHManualFrame.doc, Table of

Contents.doc.

1. ArrayTools_UpdateVersion.txt, it will keep on the ArrayTools

server.

1. http://linus.nci.nih.gov/~brb/news.html
2. Different ArrayTools installers.

a. There are 3 installers: Full, Individual and Update. Main release has no Update installers. b. Individual installer has no R and no Java installers in the Misc folder. It will detect the required R version (or newer than the required R version). If no required R version or lower, the installation will abort. c. Update installer has changed files between current and previous freeze folders.

1. The installers will keep a copy in

K:\BRB\ARRAYTOOLS\archive\installers\. Alpha versions will not keep, only Beta versions and release versions will keep on K:.

1. Yingdong Zhao puts the new release online:

a. Create a testing page: http://linus.nci.nih.gov/BRB-ArrayTools_test.html b. Whats-new-v43b1.doc, Readme.doc, License.doc, Manual.doc c. Java, R download links d. Installers: Full, Individual, Update e. ArrayTools_LatestVersion.txt f. Sending emails to users about new release need about 3 hours.

Only Beta 1 and Stable versions need to send out user emails. Other Beta versions don't send to reduce user emails.