My .02
I would think your second scenario makes it extremely difficult to
regression test code. Certainly in the Networker code there are many
dependencies on a few key modules. If updates were released for features
and separate updates were released for big fixes, the complexity would begin
to mount exponentially.
IMHO because the code is written, it should be available to all users of the
software unless it can discriminately be held separate from the primary
modules of the software.
If the dollars and sense don't work out to support this, I would think there
are other ways (increased licensing fees) to cover the development costs. Of
course they could just also force you to buy maintenance to receive any
updates at all - regardless of the nature of the update. Not good customer
service, but is what some software companies do.
-M@
Matt Shive
Black & Decker
Intel Technology
-----Original Message-----
From: Cyndi Smith [mailto:Cyndi.Smith AT ASPENTECH DOT COM]
Sent: Monday, September 29, 2003 12:17 PM
To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
Subject: Re: [Networker] FW: NW 7.1 release
I disagree. There are two situations.
If patches are to FIX problems, then they should be available to
anyone who has purchased the software.
If they are to ADD features, they should only be available to people
who have purchased update subscriptions.
I know that it is virtually impossible to write code without bugs (as a
former developer myself), but anyone purchasing software has the right to
the expectation that the software is as bug-free as the manufacturer can
make it and if the manufacturer discovers and fixes bugs, the fixes should
be available to all purchasers as a part of the original purchase price.
My 2 cents...
Cyndi
---
Cyndi Smith
Senior System Support Engineer - Unix
Aspen Technology, Houston, TX
> -----Original Message-----
> From: Ed Skolnik [mailto:eskolnik AT INTERPUBLIC DOT COM]
> Sent: Monday, September 29, 2003 11:03 AM
> To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
> Subject: [Networker] FW: NW 7.1 release
>
>
> Well I partially agree with what was said so far, but Legato
> is a business and if you don't pay for support you shouldn't get the
> patches. It's only fair to the companies who actually pay
> for support. The TEch Dialog should be updated to show what
> patches are
> out there (via logon and password) like Sun doees (free
> viewing, but patches require a account woth a password),
>
> ed
>
> -----Original Message-----
> From: Robert Loh [mailto:robert AT SOFTSOURCE.COM DOT SG]
> Sent: Thursday, September 25, 2003 3:52 AM
> Subject: Re: NW 7.1 release
>
>
> I absolutely agreed, they should make update or patches
> easily accessible to public who support Legato products.
> Veritas doing that
> pretty well, I am not supporting Veritas or Legato, I just
> said the truth, they should learn from other and improve even better.
> Always when I hit a problem, I need to escalate and diggling
> here and there and hopefully get the patches :)
>
> -----Original Message-----
> From: Hrvoje Crvelin [mailto:hcrvelin AT ORCHESTRA DOT DE]
> Sent: Thursday, September 25, 2003 3:39 PM
> To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
> Subject: Re: [Networker] NW 7.1 release
>
>
> Hi,
>
> I'm not here to defend Legato, but highest support levels
> would be premium with PSAM, right? I believe this gives You
> a right to
> PSAM bulletin which has list of recent fixes and open escalations.
>
> Some other vendors do the same, but not via bulletin but
> password protected web pages - at the end the result is the same.
>
> I agree that for big issues Legato would need to have public
> available page which gives description of the problem and patch. When
> I say big issue that would mean issue related to all
> platforms or/and issue which limits/break designed
> functionality. I guess
> there should be a formula which patch should be public and
> which available upon request. Legato does sort of thing in
> that respect
> and that has been covered by this list in the past too. The location
> is:
> ftp://ftp.legato.com/pub/NetWorker/Updates
>
> Now, many of You will find that not enough and poorly
> updated. As I said, "sort of thing". I'm not sure what is
> the Legato policy
> regarding updates of that area.
>
> On the other hand AlphaStor has the updated list of fixes
> which are available and that list seems to be updated on
> regular basis.
> This list is always available from ftp area.
>
> Perhaps someone from Legato on this list could say more...
>
> Cheers,
> .c
>
> -----Original Message-----
> From: Legato NetWorker discussion
> [mailto:NETWORKER AT LISTMAIL.TEMPLE DOT EDU] On Behalf Of Chad Smykay
> Sent: Thursday, September 25, 2003 6:25 AM
> To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
> Subject: Re: [Networker] NW 7.1 release
>
>
> I agree with your last statement. What they need is a
> webpage that lists out any current known, new issues and let
> you know about
> the patches. Hell we are one of the highest levels of
> support with them and can not get a feature like this. But
> then again this
> is an application where "if it ain't broke, don't fix it" mentality.
>
> Regards,
> Chad Smykay
>
> --
> Note: To sign off this list, send a "signoff networker"
> command via email to listserv AT listmail.temple DOT edu or visit
> the list's Web
> site at http://listmail.temple.edu/archives/networker.html
> where you can also view and post messages to the list.
> =*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
>
> --
> Note: To sign off this list, send a "signoff networker"
> command via email to listserv AT listmail.temple DOT edu or visit
> the list's Web
> site at http://listmail.temple.edu/archives/networker.html
> where you can also view and post messages to the list.
> =*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
>
> --
> Note: To sign off this list, send a "signoff networker"
> command via email
> to listserv AT listmail.temple DOT edu or visit the list's Web site at
> http://listmail.temple.edu/archives/networker.html where you can
> also view and post messages to the list.
> =*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
>
--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
|
