CVS read only access

[jaigupta]

How about a CVS read only access which will auto update your codebase?

You won't have to keep looking for bug fixes, new features, your code will always be latest and updated.

[Siora]

Becasue many users of kayako modify their code it may not be feasible for an auto update as this would not allow members to either back-up their code or note what changes they've made.

[jaigupta]

Correct, but what if they don't make changes to code? Most people who make lot of changes in code don't actually want to update because they will have to manually apply changes again.

Also if someone made changes to a single/few files he can make that file read only and update rest of the files.

If someone made changes to template then he can skip updating templates.

[ecornet]

What about unstable updates? I would really really hate coming in one morning and find out that the support is broken. Then have to try and find out what happened only to realize it was an unfinished patch..

[Jamie Edwards]

Hi there,

We won't be providing automatic updates of the server-side code (SupportSuite, eSupport and LiveResponse).

[craigbrass]

I fail to see what giving this access would achieve. A new build is made every night...

[jaigupta]

Originally Posted by ecornet

What about unstable updates? I would really really hate coming in one morning and find out that the support is broken. Then have to try and find out what happened only to realize it was an unfinished patch..

CVS has option to update only from specified branch or tag, you could use stable tag to update only stable version.

[jaigupta]

Originally Posted by craigbrass

I fail to see what giving this access would achieve. A new build is made every night...

We can relate this with windows update service, your installation is automatically patched with security updates.

[jaigupta]

Originally Posted by Jamie Edwards

Hi there,

We won't be providing automatic updates of the server-side code (SupportSuite, eSupport and LiveResponse).

I know I don't have right to ask question about internal decision of company but if you feel like you may like to tell us the reason(s) of your decision.

[Jamie Edwards]

Hi jaigupta,

As a customer, you have every right. I am sorry that my post was not very detailed. The reason why has been talked about before, and also mentioned by others in this thread - there aren't enough users who would opt to use such a service due to a number of reasons:

• The customisations that people make (in templates and their code)
• The massive issues that arise due to differing platforms and configurations
• The problems that will result if a dependency is added in a version and an upgrade is done automatically, this breaking the installation
• (Related to the point above) the massive amount of issues that will arise trying to test for these dependencies
• The security implications for the end users

It is a system that could be designed, but at enormous expense of money and time - the number of people who would actually implement this service and configure their server for it is very, very small. In this sense, it is not a feasible project. The vast majority of our customers want complete control over their upgrades and installations.

[jaigupta]

I can understand your point. Actually I wanted it

Well, I think I have been too long in open source

Thanks