<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"><html><head><meta content="text/html;charset=UTF-8" http-equiv="Content-Type"></head><body ><br>Hi Jeff,<br><br>Here after the source build will have the following naming convention vtigercrm-x.y.z.tar.gz<br><br>Philip<br><br><br>---- On Thu, 07 Sep 2006 Jeff Kowalczyk <jtk@yahoo.com> wrote ---- <br><br>Gopal wrote:<br>> I am happy to inform you that our GA validation build is ready for testing. <br>> <br>> Before announcing our public release we would like to have a final round of validation, so that we can avoid any last minute glitches.<br>> <br>> Kindly participate in this final testing and report any bugs in Trac:<br>> <br>> http://vtiger.fosslabs.com<br>> <br>> You can download the version 5 GA validation build (SVN Tag: 9353) from the following URLs:<br>> <br>> http://vtiger.com/archives/vtigercrm-5.0.0.exe<br>> http://vtiger.com/archives/vtigercrm-5.0.0-source.tar.gz<br>> http://vtiger.com/archives/vtigercrm-5.0.0.bin<br><br>If doing a validation step, the commonly used procedure is to keep<br>releasing successive rc# builds. The one that the release managers decide<br>is good enough to ship gets copied (e.g. tagged) with the final name, and<br>no changes from the accepted rc# tag.<br><br>There should never be two (pre)released filenames with different MD5<br>signatures out there, which is what we'll have if some flaw turns up in<br>validation.<br><br>Also,<br>http://vtiger.com/archives/vtigercrm-5.0.0-source.tar.gz<br>should just be<br>http://vtiger.com/archives/vtigercrm-5.0.0.tar.gz<br>source is implied in a PHP project.<br><br><br>_______________________________________________<br>Get started with creating presentations online - http://zohoshow.com?vt <br></body></html>