Re: Another take on Embarcadero and CodeGear

Alan Garny brought next idea :
"Bruce McGee" <bmcgee@xxxxxxxxxxxx> wrote in message news:xn0fq3c5qu1xtn6000@xxxxxxxxxxxxxxxxxxxxxxxxx
Paul Hughes wrote:

And before everyone starts sticking up for CG and querying how many
QC reports you've posted/voted on I would simply say - we shouldn't
have to. All those things should have been attended to/fixed as a
matter of course. This voting on QC should be reserved for free
software where resources are stretched - not for stuff that a lot of
people have paid top dollar for.

Oh, heaven forbid.

Given that time and resources are finite, what is your alternative?

I don't know whether there is an alternative, but you will have to agree that paying top dollar for a product and then be asked to submit/vote for bug reports is a bit much, especially when you are told that you are not precise enough in your bug report(s), when your bug report(s) are being ignored, etc.

It takes 'skills' and time to write a good bug report and not everybody has such skills or time. I, for one, don't have the latter.

We have users that pay thousands of dollars for our software
and then thousands more in annual maintenance fees.
They don't seem to have any problem with using our CRM
system to submit fix requests and enhancement requests.
A significant number of the fixes are submitted by our
support staff as they work with customers, but there are
a lot that come straight from the customer.
These are reviewed once a week. We look at the footprint
of the issue. Allen's comments on this point were helpful.

Some are accepted immediately. Since we deal with bank
data, any bug that involves incorrect data gets a high
priority. But everything gets a priority.
Anything that doesn't seem top priority to us to be
worked on immediately, get published so that everyone
else can vote on it.
Issues that get more votes get moved up in priority.

We end up working on a lot of things that we didn't
expect to, just because they got voted on.

I don't see the problem.

HTH,
Brad.


.

Relevant Pages

  • Re: Suggestion to Borland : Public betas!
    ... back and vote when the reports finally gets opened. ... requests are feature requests. ... Bug reports, almost by definition, are only interesting to the poeple ...
    (borland.public.delphi.non-technical)
  • Re: Delphi 6 vs C# speed comparison
    ... > everyone had 100 need points to spend, and different reports in QC ... > people still vote for the new features they ask for if doing so made ... pleading with people to get bug reports into QC, ... bug reports (as opposed to feature requests) then you can't complain ...
    (borland.public.delphi.non-technical)
  • Re: Just random fixes with QC reports...
    ... then vote for it to be ... If this bug doesn't affect your code and it doesn't impact anyone ... is so buggy and Borland is being so slack about fixing QC reports, ... Fixing all bugs isn't even remotely realistic. ...
    (borland.public.delphi.non-technical)
  • [Un] Unangband 0.6.1 beta 6 released
    ... I\'ve had lots of bug reports and feedback, as well as a winning character since ... if the value on the damage dice roll is less ... Fixed bug when describing sense item effect. ...
    (rec.games.roguelike.angband)
  • Re: kernel bugzilla is FPOS (was: Re: "buggy cmd640" message followed by soft lockup)
    ... Andrew is going through all new bug reports. ... People like Natalie or me also go through new bug reports. ... You can always ask on the list, pointing to the Bugzilla entry in question. ...
    (Linux-Kernel)