Hi jimicus! Yes, the 30/10/3006 build had issues. vtiger had done a lot of work in the past on the migration front but somehow it reached a peak of fiasco in that build. So I guess, you were upset. This time around, we have been focussing a lot on the migration and also on the migrated build. As earlier, the UI is embedded within the product and we have made some additional fixes in it as well. We have tried to cover as many loopholes as possible this time.
As ever, things are perfect in a developer environment. I am myself keeping my fingers crossed as to how things go when it goes live into the market.
Jimicus, yes, we had/have flaws in our system. Let me assure you that we have tried to address a majority of these kinds of issues in the 5.0.3 release. In fact, because of the fact that we decided to address the host of issues that were present, the release was delayed by around 4 months or so.
The last vtiger release 5.0.2 was on 30/10/2006. 7 months have passed since then and we are about to release the 5.0.3 now.
I hope you will like this release.
Thanks for voicing your opinion. Appreciate it. BTW, we are working on the last observation of yours too.
Hi! I am Richie from vtiger. Yes, of late, the release has been very late by vtiger standards. This was done so that the quality issues are addressed. Earlier on, vtiger was more date-driven and hence had compromised on the quality and user-experiences. This time around, quality is the paramount factor in mind. Hence the extended time before we release.
The last release was on 30/10/2006. It has been 7 months now since the last release. The new release is due this month and will be primarily a bug-fix release.
Pertaining to the original discussion, I would agree with jimicus. Open Source is not a silver bullet. You will have to be very careful in what you want and how you would like to achieve the same. I would suggest Open Source since you will have multiple alternatives but at the same time, you have to be careful as to which horse you back even in the OS domain. Priorities change depending on the community response to the releases so what you want may or may not be in the next release.
Try and build modular plugins/extensions so that you can replace them with anything new that comes in. This way you will be uptodate and not be hampered by progresses. You will not be able to do this with Commercial products though.
Slashdot Mirror
Hi jimicus!
Yes, the 30/10/3006 build had issues. vtiger had done a lot of work in the past on the migration front but somehow it reached a peak of fiasco in that build. So I guess, you were upset.
This time around, we have been focussing a lot on the migration and also on the migrated build.
As earlier, the UI is embedded within the product and we have made some additional fixes in it as well.
We have tried to cover as many loopholes as possible this time.
As ever, things are perfect in a developer environment. I am myself keeping my fingers crossed as to how things go when it goes live into the market.
Richie
Jimicus, yes, we had/have flaws in our system. Let me assure you that we have tried to address a majority of these kinds of issues in the 5.0.3 release. In fact, because of the fact that we decided to address the host of issues that were present, the release was delayed by around 4 months or so.
The last vtiger release 5.0.2 was on 30/10/2006. 7 months have passed since then and we are about to release the 5.0.3 now.
I hope you will like this release.
Thanks for voicing your opinion. Appreciate it.
BTW, we are working on the last observation of yours too.
Thanks,
Richie
Hi!
I am Richie from vtiger.
Yes, of late, the release has been very late by vtiger standards. This was done so that the quality issues are addressed. Earlier on, vtiger was more date-driven and hence had compromised on the quality and user-experiences. This time around, quality is the paramount factor in mind. Hence the extended time before we release.
The last release was on 30/10/2006. It has been 7 months now since the last release. The new release is due this month and will be primarily a bug-fix release.
Pertaining to the original discussion, I would agree with jimicus. Open Source is not a silver bullet. You will have to be very careful in what you want and how you would like to achieve the same. I would suggest Open Source since you will have multiple alternatives but at the same time, you have to be careful as to which horse you back even in the OS domain. Priorities change depending on the community response to the releases so what you want may or may not be in the next release.
Try and build modular plugins/extensions so that you can replace them with anything new that comes in. This way you will be uptodate and not be hampered by progresses. You will not be able to do this with Commercial products though.
Richie