<!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 Team!
<br>
<br>I guess we have to make the call sooner than later. Let us get on with this tonight.
<br>We will be updating the demo on a regular basis from now on so that we get all the feedbacks before the Beta release scheduled tentatively for Wednesday, the 24th of May.
<br>
<br>Allan, JeffK , go ahead and merge the changes please.
<br>
<br>Richie<br><br><br><br><br>---- Jeff Kowalczyk<jtk@yahoo.com> wrote ---- <br><br><blockquote style='border-left: 2px solid #0000FF; padding: 6px;'><html>
<xbody>
Allan Bush wrote:<br>> Richie,<br>> Postgres is coming along, not as quickly as I had hoped but it's getting<br>> there. The installation process is working now and their aren't too<br>> many problems with normal navigation.<br><br>To clarify, Allan's changes aren't expected to impact mysql users in any<br>way. Postgresql support will take some time to achieve parity with mysql<br>support, but that shouldn't interfere with your normal<br>vtigercrm-5.0.0beta1 release objectives. I think its fine to say in the<br>release notes that mysql support is farther along than postgresql for this<br>beta.<br><br>> The biggest hurdle right now (other then just plain lack of time on my<br>> part) is with the state of flux of the code base. Jeff is doing a great<br>> job syncing the branch up all the time, but the large amount of change<br>> requires a lot of re-testing on our part. I think the best course of<br>> action right now is to merge the branch back into the trunk.<br><br>Allan, Joel and I have discussed this, and concur. Keeping everyone on the<br>trunk will increase the amount of eyes for testers.<br><br>> Mering the postgres branch this will free up more time for Jeff to work<br>> on other fixes<br><br>Yes, I'd prefer to be working on whitespace cleanup of SQL queries in the<br>trunk.<br><br>> and I don't foresee any more breakage as all changes from here on are<br>> simply fixing queries one at a time as we come across problems.<br><br>This is the reason I want start cleaning up the formatting of SQL right<br>away. Allan's changes to make proper use of adodb (where are not<br>presently) will be a general bug fix, IMHO. The fact that they enable<br>postgresql support is just the initial benefit, leading to wider database<br>backend support later on.<br><br>> The biggest advantage I see with dropping the branch is if we find a bug<br>> we won't have to concern ourselves with if it's a postgres only bug or<br>> not and we'll just be able to fix it without worrying about duplicating<br>> the effort of one of your guys.<br><br>> this will allow us to split the long sql queries into multiple lines so<br>> that SVN can track the changes better<br><br>This is the main benefit. I want to see queries use many vertical lines,<br>so that the pending release and maintenance branches can become mergeable.<br><br>> Merging the branch just before the next validation round would be<br>> prefect timing and unless Jeff or Joel say otherwise I think it's ready<br>> to be merged at anytime now.<br><br>Unless anyone objects, I'd like to do this soon. I would merge at the end<br>of the vtiger team's workday. Anybody having a preference for the best day<br>to do it, speak up.<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>