[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[cobalt-users] Cobalt Users responsibility to test before deployment ? (from thr ead Webalizer 13.->2.0 RAQ3i)
- Subject: [cobalt-users] Cobalt Users responsibility to test before deployment ? (from thr ead Webalizer 13.->2.0 RAQ3i)
- From: "Vachon, Scott" <Scott.Vachon@xxxxxxxxxxxxxx>
- Date: Wed Nov 15 08:07:01 2000
- List-id: Mailing list for users to share thoughts on Cobalt products. <cobalt-users.list.cobalt.com>
>I am in hosting business. I think people in hosting
>business have no time to lose or play. We want issues to >be resolved
immediately. As our clients
>expect their problems to be resolved immediately because >they are paying
us for the service;
The question we should ask ourselves then is, "Does the client want quick
and sloppy fixes, or are they paying us in trust that the service/product we
provide is tested, stable, and secure and we are fully knowledgeable about
it ?
>However, I see that they are lacking in certain areas and >noticed that
their target is to get our money whatever
>the reason is.
Well yes, our suppliers (Cobalt in this case) is in business for profit. It
behooves them to sell high volume in short time blocks and then limit
expenses (such as support) by staffing support at a level only high enough
to keep the majority of customers from buying elsewhere and/or keeping
complaints down. As, well, the less product they replace/repair with
supplies and the more that instead goes out as new sales is also in their
best interest. Sucks for us though..as you note.
So again, knowing as you do that their support is not as good as which you
provide your customers (or Cobalt users as a whole to "our" customers) isn't
there a responsibility on our part to test new patches on test platforms as
thoroughly as possible before deploying them live to our customers ?
--S--