<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Hi Frank,<br>
<br>
Thanks for your feedback. We'll try to post a validation builds if
possible for our addons before our 5.0.3 release. But we'll make it a
point to go with addons along with our validation build in future.<br>
<br>
We are trying to achieve a version that is as stable as possible. Once
5.0.3 is out we have to decide on the next version based on the
features and bugs that are left out. We'll check that the trac is in
tune.<br>
<br>
Regards,<br>
Philip<br>
<br>
<br>
<br>
Frank Piepiorra wrote:
<blockquote cite="mid000401c73247$3d682250$0400a8c0@frank1jqxubzza"
type="cite">
<pre wrap="">Philip,
These are good news and I hope that the testing of this version will
lead to a better product soon. In order to be able to fully validate
this release I think we should cover the entire package of the CRM core
product and its extensions/plugins. Users do not appreciate a better
core product very well if there are new problems with CRM extensions
they use.
For instance, in the previouse releases there had been also releases of
the outlook plugin (v5.0.0, v5.0.1, v5.0.2). Each of them behaved
differently. Unfortunately, these releases where not very well
documented and did not have any release notes at all. So I would like to
suggest to make these extensions part of the validation process and to
include release notes for the extensions/plugins when you make your
public release. Would that be possible?
You provided an impressive list of bugs that has been fixed. But the
list of open bugs at the tracker confuses me. While most of the bugs
have now a milestone there are many bug marked with version 5.0.2 or
older that do not have a milestone. What does that mean?
There are also a large number of bugs that have moved to the milestone
5.1.0. As I understand your release policy 5.1.0 will not be a bugfix
release but a feature release. If that is correct why moving bugs fixes
to 5.1.0 and not to v5.0.4?
Regards,
Frank
</pre>
<blockquote type="cite">
<pre wrap="">Date: Sat, 06 Jan 2007 15:50:00 +0530
From: Philip <a class="moz-txt-link-rfc2396E" href="mailto:philip@vtiger.com"><philip@vtiger.com></a>
Subject: [Vtigercrm-developers] Validation for 5.0.3 starts
Hi Developers,
We have started the validation phase for 5.0.3 and our core
team is testing the product for any critical bugs.
Before going in for public release after validation, we want
ourcommunity developers to test the product and give us the
feedback ofany critical issue.
We have hosted the 5.0.3 (test) build in <a class="moz-txt-link-freetext" href="http://en.vtiger.com/wip/">http://en.vtiger.com/wip/</a>
Do post your feedback in
<a class="moz-txt-link-freetext" href="http://vtiger.fosslabs.com/cgi-bin/trac.cgi/newticket">http://vtiger.fosslabs.com/cgi-bin/trac.cgi/newticket</a> under
"Version" 5.0.3-dev
We have tagged the source in fosslabs the source can be
checked out from the following url
<a class="moz-txt-link-freetext" href="http://vtiger.fosslabs.com/cgi-bin/trac.cgi/browser/vtigercrm/">http://vtiger.fosslabs.com/cgi-bin/trac.cgi/browser/vtigercrm/</a>
tags/vtigercrm-5.0.3-rc
Regards,
Philip
Note:
1) Migration script for migration from other versions and
patch zip for existing users 5.x will be sent latter.
2) Release Notes has not been updated this will be captured
during release.
</pre>
</blockquote>
<pre wrap=""><!---->
_______________________________________________
Reach hundreds of potential candidates - <a class="moz-txt-link-freetext" href="http://jobs.vtiger.com">http://jobs.vtiger.com</a>
</pre>
</blockquote>
<br>
</body>
</html>