<!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 >Hi!
<br>
<br>The 4.2.4 is available for download at the following location :-
<br>
<br>http://vtiger.com/download/vtiger_CRM_4_2_4.exe
<br>http://vtiger.com/download/vtiger_CRM_4_2_4.bin
<br>http://vtiger.com/download/vtiger_CRM_4_2_4.PhpDocs.zip
<br>
<br>The source will be released soon as there is a small logistical problem here
<br>causing the delay.
<br>
<br>Let me know if there be any issues.
<br>
<br>Should we make this an official announcement Allan?
<br>I would prefer if you do it as you have taken the initiative.
<br>It is only right that the credit too is taken by you.
<br>
<br>Richie
<br><br><br><br><br><br>---- Allan Bush<allan.bush+vtiger_dev@gmail.com> wrote ---- <br><br><blockquote style='border-left: 2px solid #0000FF; padding: 6px;'><html>
<xbody>
Thanks guys,<br><br>I've tagged and exported 4.2.4 (without changes) and it's ready to go.<br> I also created some release notes, attached to this email if anyone<br>has any input on them.<br><br>I sent this information along with the packaged release to richie but<br>as he seems to be unresponsive on this release I'm not counting on him<br>to get it out in a timely manner. I'd like to put the release on the<br>trac system, if the admin is alright with that please email me<br>directly and I'll get you the files, if not I'll just attach it to the<br>vtiger message board.<br><br>On a side note the trac ticket system should be modified to remove<br>4.2.4 as a milestone and add it as a version (and probably remove the<br>4.2.4rc's well we're at it), if that can be done without messing up<br>the existing tickets.<br><br>Allan<br><br>On 5/30/06, Jeff Kowalczyk <jtk@yahoo.com> wrote:<br>> Brian Devendorf wrote:<br>> > I would prefer 4.2.4 gets released, as 4.2.3 has so many known bugs.<br>> > I think it would focus the bug reporting for vtiger 4 on the bugs<br>> > that still exist in the product.<br>><br>> Sure, its always good to have extra point releases to eliminate patch<br>> trading. vtigercrm-4.2.5 will likely follow soon after.<br>><br>> Based on past tags, our procedure was to put the branch in the exact form<br>> used for release, then copy to a tag using the command:<br>><br>> # svn cp (url)/vtigercrm/branches/4.2.4 (url)/vtigercrm/tags/vtigercrm-4.2.4 -m 'Tag 4.2.4 for release'<br>><br>> Ideally (and we may not be there yet), a release fileset is a<br>> vtigercrm-4.2.4.tar.gz and vtigercrm-4.2.4.zip made from:<br>><br>> # svn export (url)vtigercrm/tags/vtigercrm-4.2.4<br>><br>> With no post processing. I guess for .exe installers (if used), that's an<br>> exeption to the rule.<br>><br>> Unless there are any changes to forward port to branches/4.2, we finally<br>> svn rm the branches/4.2.4.<br>><br>> Thanks for doing the release, Allan.<br>><br>> _______________________________________________<br>> This vtiger.com email is sponsored by Zoho Planner. Still scribbling down your To-Do's on bits of paper & palms of your hands? Try the AJAX enabled, personal organizer online, Zoho Planner for FREE instead! <a href="http://zohoplanner.com/?vt">http://zohoplanner.com/?vt</a><br>><br>_______________________________________________<br>This vtiger.com email is sponsored by Zoho Planner. Still scribbling down your To-Do's on bits of paper & palms of your hands? Try the AJAX enabled, personal organizer online, Zoho Planner for FREE instead! <a href="http://zohoplanner.com/?vt">http://zohoplanner.com/?vt</a> <br>
</xbody>
</html></blockquote></body></html>