Stable Build

[Jamie Edwards]

Hi clyde;

The CVS is a concurrent versioning system, which allows a group of people make changes to one product or program whilst maintaining a synchronised version - so everyone is working on the same thing.

Typically of a CVS system, they are generated nightly or whenever a change is made.

I personally run 3.10.00 (CVS version) and have done for a while, as it contains a multitude of bug fixes and several feature additions.

However, running CVS versions is not recommended for mission-critical set ups.

Until an official Stable build is released, you could backup your help desk files and database and do the upgrade - if things don't work out, you can always roll back quite easily.

You can check the changes that have been made here: http://builds.kayako.net - see if any bug fixes or feature additions are particularly applicable to you. If they are, you might see upgrading to a CVS as a good option. If they are not, you can play it safer and wait for an official Stable

- Jamie

[clyde]

Many thanks Jamie, excellent clarification

[skaye]

This is complete rubbish, we were told a Stable build was days away over a month ago. My confidence in Kayako to deliver anything on time is eroding rapidly.

[keliix06]

Originally Posted by skaye

This is complete rubbish, we were told a Stable build was days away over a month ago. My confidence in Kayako to deliver anything on time is eroding rapidly.

That's one thing you'll unfortunately need to get used to. One reason they don't like giving ETA's too often is that they are never met. Useful tip is to add 4-8 weeks to most dates, especially if the timeline given is over 24 hours.

[Jamie Edwards]

Hi,

As you can see from http://builds.kayako.net - there is still work being done on the current UNSTABLE build that will eventually become the new STABLE fixing some important bugs that are becoming apparant during the intensive testing phase by the Kayako testers.

I'm sure you'll agree that Kayako do not want to release an unstable STABLE build, so these bugs must be ironed out.

As you have pointed out, giving ETAs (even though pressed for giving them out publically) isn't always a brilliant idea for any software developer as they cannot predict how many or what bugs are to be found in their latest version.

If developers could predict this, the world would be a much better place!

Do stay tuned, though - the developers are working hard (as you can see from the change log), the testers are working equally hard finding the bugs and I'm at work producing documentation for the 3.10.00 version.

[sureshkumar.mr]

Originally Posted by Jamie Edwards

the developers are working hard (as you can see from the change log)

I can see only 4 additions in the change log from past 16 days...

I don't know whether they are working hard or hardly working... (Sorry guys, just kidding)

[Coastie]

Originally Posted by skaye

This is complete rubbish, we were told a Stable build was days away over a month ago. My confidence in Kayako to deliver anything on time is eroding rapidly.

We waited for v3 for over a year past when it was due, and when it came it was unusable, and for me still is

[triller]

In my case, I nearly escalate the unicode search problem for one year, never get a serious answer whatever by ticket, forum or live chat.

Kayako support to me is totally invisible...

[Hermelin]

Oh, last change:

Files Affected: 4
Notes: SWIFT General:
- Added feature of ticket sorting in Support Center.

Sounds good....

I look forward the next stable build!