Ticket hover preview STILL showing HTML

[NC Software]

I thought this was supposed to be fixed in the latest stable? It's not, see attached!

[Jamie Edwards]

Kayako Bug Tracker - Viewing Issue #212 - Tags not stripped in mouse-over preview

It is fixed in the current CVS build (3.20.03) - if you're not running this build you will not yet have the fix.

[supportskins]

Mind it, Kayako does not recommend you upgrade to a CVS build.

[NC Software]

I used a CVS build long long ago, never again, what a chocolate mess! That's why I wish we'd see more frequent STABLE builds so we don't have to wait eons for security fixes and orphaned ticket issues like can occur with the screwed up assignment drop downs, etc.

[craigbrass]

That's why I wish we'd see more frequent STABLE builds

I disagree. I would prefer less stable builds as upgrading means reapplying modifications and redoing templates. In some cases, language packs too.

[Siora]

It would be nice to have hotfixes that can be applied without the need to upgrade to a new build. I would think that a hotfix would be a good compromise between the two sides and would allow customers to keep their installs secure rather then waiting for a stable build.

[Jamie Edwards]

Originally Posted by Siora

It would be nice to have hotfixes that can be applied without the need to upgrade to a new build. I would think that a hotfix would be a good compromise between the two sides and would allow customers to keep their installs secure rather then waiting for a stable build.

It is something we would like to be able to do too. Unfortunately, it is simply not possible - there are too many dependencies created between builds that may relate to fixes.

Currently, development and work on clearing the bug tracker is at a very rapid pace. Once our release cycle has stabilised, it is a question we will revist.

[Siora]

I agree Jamie however there needs to be some sort of balance because upgrading builds forces a lot of people to redevelop their sites costing more money just to keep their product secure. Maybe you could come up with a way to do a complete build update but avoid touching templates. If templates need to be changed then maybe they can be applied by either letting people know the changes in the templates or applying fixes to the changes in such a way that your customers don't have to redo all their templates.

[PeteV]

Craig,

if you do not like frequent stable builds, then you can just skip as many as you like. Users having to upgrade templates, etc. is not a good reason for Kayako not to release stable builds whenever feasible (and as frequent as possible).

It is up to the users to decide whether upgrading makes sense. It is obvious that a significant number of people are still using eSupport v2.

Pete.

[NC Software]

I agree that stable releases should be posted more frequently, monthly, every other month, when sufficient fixes are available, etc. The user doesn't have to update with every published stable release, if they have a complex configuration they may choose to wait, or wait for specific issues that affect them to have been resolved.

Microsoft is actually working to get more frequent updates out to developers, they are doing hotfixes now, service packs more frequently, etc. You (K) are only making us suffer with your untested mess-ups (the combo issues), unfixed bugs reported long ago (html in ticket preview - security issue!), on and on. It is up to you whether you want to provide a good service to your customers and get stable releases out more frequently to prevent our pain and suffering. It's your commitment to quality, it's up to you.