Busy Holidays - 5.0.4 update
December 18th, 2007 by svk
Our team is working hectically on fixing bugs found in the last round of validation. Most of the recently identified issues are to do with UTF-8 support in the vtiger plug-ins. We only uncovered them in the latest round of validation. We are improving the test process to catch these early and putting the product through rigorous testing focused on Security, data integrity, and functionality.
At this juncture we feel it is important to spend the extra few days, to address the critical and major issues before releasing the product. Its going to take us another 5-6 days to complete this process, which puts us right in the middle of the “holiday week” between Christmas and New Year. Instead of releasing it that week, we have decided to release 5.0.4 in Jan 1st week. We will be using the extra few days to update the documentation, and get the product ready for release.
We apologize for the delay, and would like to assure you that the team is working hard on completing some important bug-fixes and putting the finishing touches.
Help others find this article: 
|
|
|
|
|
Posted in General | | Post Comment | Permalink | Trackback
yeah, super!!
thenk you for all
have good work!
Thanks for the update, and for all your hard work.
Great. I was hoping for it to be released before Xmas but, I understand that releasing a stable product is more important than an early release.
Brilliant work. Happy Xmas to you all !
Stable is most important. Thanks for all of your hard work!
Thanks for update !
Thank you for the info. One reason more to be next year
Thanks for the update. I agree, stable is better (plus, putting out a “stable” release at Xmas would have been a pun overload).
Thank you for the update!
I know you are all doing your very best!
I’m just disappointed because I wanted it so much before x-mas, to have the possibility to work on it over the holiday shutdown… I know, that’s my personal problem, but I’m still kind of sad, sorry for that.
Keep on going…
Tom
~__~ I HEAR THE VTIGER BELL RiNgInG ~__~
Great work an d Merry Christmas to all at vTiger!
Good news! I hope that there will be a migration possible from 5.04 RC2 to 5.04 stable???
Great news and many, many thanks.
I wish you all a merry X-Mas and a happy new year.
I am looking forward to implement the new 5.0.4 version.
But as my forerunners already posted: Stable is most important
Hey, that’s really good news again!
Wish you a merry x-mas despite all the remaining work
We are anxiously awaiting the release of 5.0.4. We are going to be doing a completely new install and we’re waiting for 5.0.4 to do all the customization. Looking forward to trying it out.
Thanks for all the hard work vTiger team!
1st week of jan is over in a minute or two.
Any news on when 5.0.4 is out?
John, Robert: Sorry for the inconvenience.
We are almost there! We will be announcing the release on Monday/Tuesday.
Sreenivas
vtiger Team
That’s amazing news! Thanks guys and gals!
Hi guys,
I can’t await 5.0.4… but it really helped me to look into the “Bug Tracker”!
You can see the progress day by day:
http://trac.vtiger.com/cgi-bin/trac.cgi/roadmap
Bye,
Tom
After a rough first try with vt 4.2, i have installed 5.0.3 a week ago, now with a dedicated resources to the proyect, so, do you recommnd to install 5.0.4 instead?, i´m using es_es, lang pack,
thanks in advance for any comment related
Victor
Any news about 5.0.4 ?
I see in trac roadmap 5.0.4 still have 40 Active tickets.
I’m hoping today is the day.
Everyone, you can check on the status of the release validation here: roadmap There are currently 33 active tickets open (read: 33 bugs to fix). If you click on the “33″ number, you will see the detail of what’s left to do. Note that this number of open tickets will fluctuate up and down as validation continues.
I’m not part of the team, but my best guess as an outsider would say that 5.0.4 will be here in around 5-10 days.
There is a chance that those bugs are fixed but haven’t been closed yet….
It’d be disappointing if it was that long being as they said monday or tuesday. I’m not sure they’ve ever announced a release date that was even vaguely correct!
I was very disappointed, too. But the main reason was, that I didn’t know what to expect when. That’s why I can higgly recomend to follow that link above and check the open tickets, see the direction and how they develop…
Then everybodywould understand why they said Tuesday and cannot hold it now.
From my point of view it will not be this week, maybe not next week…
They are really busy and they do very good job in checking wether their system is stable!
i think they’re not happy about not fullfilling commited dates, but I hope that they are not to frustrated about that and keep on doing a great job
Bye,
Tom
Folks, We were about to put out the release candidate today, and got into a glitch with packaging. It is set to be out tomorrow (hopefully!).
As some of you have pointed out, there are still some open tickets including some concerning UTF-8. We believe there are still some untested aspects of UTF-8 which we have not covered during our QA. After putting out the release candidate version, we hope to receive your feedback and address any key issues that are uncovered in the next few days. We plan to release the final version soon (i am hoping to not commit to any dates henceforth!!)
Thanks for your understanding and support.
I echo Tom’s sentiments. The reason the number of open active tickets goes up and down, and hence moves the release date, is just the normal reflection of a proper software development cycle; that is, in the final phase, where 5.0.4 is now, they (re)test and (re)validate the code whenever modifications (bug fixes) have been implemented. While this adds delay, we should be heartened by the fact that the delay comes from “doing the right thing” (as opposed to just being sloppy or trying to cram in loads of last minute features). Plus, I’m sure v5.0.4 (like v5.0.3) is fixing some backbone issues that were inherited yonks ago. There will still be bugs in the release, but over the last 18 months I get the feeling there is a real drive to produce good, stable code. There is no real alternative.