Board index » delphi » QC Admins on vacation?

2005-05-24 01:24:41 AM
delphi124
There is no activity inside the qualitycentral area, and noone have looked
at my new functionality request for TSOAPDatamodule (12979).
Hope they get back soon...
-Atle
 

At 19:24:41, 23.05.2005, Atle Smelvær writes:
to approach the idea, since I have no experience with SOAP (to avoid any
puns: I mean the technology, not the substance) at all.
--
Rudy Velthuis [TeamB] velthuis.homepage.t-online.de
"From the moment I picked your book up until I laid it down I was
convulsed with laughter. Some day I intend reading it."
- Groucho Marx (1895-1977)
 

"Atle Smelvær" <XXXX@XXXXX.COM>writes
the request Saturday morning. You posted this message at noon on Monday. I'm
sure you feel the squeaky wheel gets the grease, but someone who likes that
kind of attitude can apply the grease then.
--
Dan Miser
www.distribucon.com
 

Well, reports like this just takes a moment to read through and open. So
why do you have a problem with that?
Is it so terrible to do something fast. I am just using the possible
channels to make information available to you. So why shoot the messenger.
Be happy that I make these reports, and open them so that Borland and the
developers can have use of them.
-Atle
 

Atle Smelvær writes:
that's not just a "side effect"... so? Should I complain for that?
I'm confident that they're working on the things, but that is not the
only thing they have to do.
Andrew
 

The vacation text is ofcourse out of line on this particular report. It's
more directed to the problem that still a very big amount of bugs have not
been looked over. A lot of reports are "reported" and not done anything
about. This have been a problem from day one. How could you else explain
2584 "reported" reports dated from 26. february 2002 till now. All
reports should be read and opened/closed. Only reports within a week or
two should be "reported".
-Atle
 

AFAIK QC Sysops are not Delphi employees (at least the majority of
them). They aren't obliged to spend their weekends checking new QC
reports <g>.
If we want quicker responses, then we should ask Borland to enhance QC
syspos motivation somehow (I've already posted my POV in another thread)
<Clarification>I am not a sysop and don't want to be </Clarification>
Atle Smelvær writes:

Another thing.. Total report amount on the Delphi project: 4899
That means that 52,75% of the reports are still just "Reported".
Do anyone think that this is acceptable? And no excuse about the
voluntaire work of the QC Admins. If they can not handle this, then Borland
should have someone to clean it up. After all, it is Borland's
responsibility to keep QC working. People are using a lot of efforts in
writing all those reports.
-Atle
 

I added a QC entry October 2002 (2621) that is still at the Reported stage.
Have they been on holiday all that time?
Unsurprisingly my faith in the QC system is a little low
Chris Bell
"Atle Smelvær" <XXXX@XXXXX.COM>writes

Chris Bell writes:
fixed in Delphi 7, but the QC entry hasn't been updated.
I'm thinking there are a bunch of reports like these. Please report
any you find.
--
Regards,
Bruce McGee
Glooscap Software
 

The Borlander who has fixed the issue should also put the QC to fixed.
Is it to much work?
"Bruce McGee" <XXXX@XXXXX.COM>schrieb im Newsbeitrag

Max writes:
one could simply let Borland know about the oversight so it can be
fixed. Why not lend a hand?
--
Regards,
Bruce McGee
Glooscap Software
 

Max writes:
-- mark it fixed in Borland's internal system. Borland R&D engineers
are not charged with maintaining QC.
So how should QC be updated? When the report is opened it will be
linked to the internal system report. When the fix is released the
status will be pushed to QC from the internal system.
This is *brand new* functionality in QC and -- as we've seen with
D2005 SP 3 -- Borland is still getting the kinks out of the system.
But that is neither here nor there for this report. It isn't marked as
fixed because it was never linked to the internal system report. I've
just done that, but I need to figure out whether it was fixed in the
original release of 7 or in SP 1 before I can mark it as fixed (IOW: I
need the xact version number).
working in a company the size of Borland. it is not "too much" because
the benefits are proportionate to the work involved. But trivializing
it doesn't help much.
--
Craig Stuntz [TeamB] . Vertex Systems Corp. . Columbus, OH
Delphi/InterBase Weblog : blogs.teamb.com/craigstuntz
Useful articles about InterBase development:
blogs.teamb.com/craigstuntz/category/21.aspx
 

Chris Bell writes:
The proper behavior is that when C is pressed, the /first/ item
beginning with C is selected. Such is the case now.
Subsequent presses of C don't move the selection. If you want it to do
that, then put that in as a feature request. Currently, the Win32
control that TListbox wraps up doesn't support that.
--
Nick Hodges -- TeamB
Lemanix Corporation -- www.lemanix.com
Read my Blog -- www.lemanix.com/nick
 

Atle Smelvær writes:
reproduce every report. Specially and most of the reports do not have
enough info or clear steps.
Yes, more active QC users and more sysop seems like a solution. If you
have suggestions on how to improve the users participation and the
quality of reports, I would like to hear then.
And as I have said in another ocasion, just like Dan Miser, I don't like
the squeaky wheel attitude.
--
Leonel