5.0.3 objective
December 13th, 2006 by Richie
The objective of 5.0.3 is to have an extremely stable product with focus on Usability. Frank has pointed out quite a few areas of Usability and the same has been pointed out to the team and I expect that some of the them will make it into 5.0.3.
As Radiant has already posted before, he too is working on some usability areas. I believe vtiger UI is mature now but the usability will take some time. Again, to be honest, usability is a journey and it will take us some time to reach there.
I want the 5.0.3 to be a work of art which lives long and lives well. I expect the next release to take quite some time and effort.
I also realise that releasing fast and frequent puts the users and the custom-deployers to quite an inconvenience. So, there will be more sanity in the release systems from now on.
Please use the trac alone as the single point of contact regarding the bugs/features/contributions. This will make the job a whole lot easier.
All moderators are requested to be very strict in the postings in the forum and pointing out the areas where the stuff are to be posted. This will make the product development much much easier and also the experience for the community members. Those interested in being moderators, kindly touch base with gopals at vtiger dot com.
Help others find this article: 
|
|
|
|
|
Posted in General | | Post Comment | Permalink | Trackback
What about printing usability?
Hi Bill!
Could you please elaborate on what you mean by that?
It will help me to consider what needs to be done and give you a proper answer please.
Richie
Hi Richie,
i think Bill speak simply about print function for all detailview (accounts, contacts, leads, calendar…).
Any chance of continuing to do a series of maybe monthly point releases while you work through the bugs, then work on v5.1 for the new features? With another release or two you should be able to get it really very solid for building new features, but the number of issues in the current system is a bit overwhelming. Also, you should set error_reporting to E_ALL, it really is quite enlightening