Resending using Tania’ template:
1. Explain why
you believe this is a stop-ship defect. How does the defect manifest itself,
and how will users of COSMOS / consuming products be affected if the defect is
not fixed?
This
is not a stop-ship, but since we are rebuilding for other reasons and this is a
low risk change, then I’m requesting that we include it.
2. Is there a
work-around? If so, why do you believe the work-around is insufficient?
The workaround is to use the COSMOS UI query builder. But
the query builder requires the query to be constructed manually each time,
which is time consuming, especially for complex queries.
3. Is this a
regression or API breakage? Explain.
Yes, it is a regression since i9.
4. Does this
require new API?
No
5. Who
performed the code review?
No one has reviewed the Cosmos Client application (as far as
I know).
6. Is there a
test case attached to the bugzilla record?
I will update the demo instructions to include test cases.
7. What is the
risk associated with this fix?
Low risk since it only involves the Cosmos Client
Application
8. Is this fix
related to any standards that COSMOS adheres to? If so, who has validated that
the fix continues to adhere to the standard?
No
From:
cosmos-dev-bounces@xxxxxxxxxxx [mailto:cosmos-dev-bounces@xxxxxxxxxxx] On Behalf Of Muldoon, William H
Sent: Thursday, April 24, 2008
11:10 AM
To: cosmos-dev@xxxxxxxxxxx
Subject: [cosmos-dev] Request
approval for "228200: Cosmos Clientregression: cannot submit queries"
Hi
I would like to request approval for “228200 Cosmos
Client regression: cannot submit queries” for inclusion in
COSMOS
i10.
It is a regression issue in i10. This is a very low risk
change that only impacts the command line client application.
Thanks
Bill