Ted,
We reviewed this on the PMC call today. We'll go with a one bug system to start - no need to open refering bugs. Jeffrey will post an updated process proposal.
Arthur Ryman,
IBM Software Group, Rational Division
blog: http://ryman.eclipsedevelopersjournal.com/
phone: +1-905-413-3077, TL 969-3077
assistant: +1-905-413-2411, TL 969-2411
fax: +1-905-413-4920, TL 969-4920
mobile: +1-416-939-5063, text: [EMAIL PROTECTED]
| "Ted Bashor"
<[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED] 03/14/2006 01:41 PM
|
|
I assume that if I want to request hot bug status for a bug I didn’t originate, I open a new [hotbug_request] bug that references the real bug report. And if/when my request is accepted, you will either change the prefix on that bug to [hotbug] or open another referencing bug with that prefix. Is that right?
If the decision is to track open hotbugs via a referencing bugs, then perhaps, for consistency, even if I originate a bug report that I want to be hot, I should be required to create the hotbug request in an external bug report?
If we do this, then I don’t think we need both the [hotbug] and [hotbug_request] prefix, just [hotbug] will do. By definition, all [hotbug] reports where the requested target milestone doesn’t match the target milestone in the referenced bug are in the “request” state. Just trying to make less work for you, Jeff J
-Ted
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jeffrey Liu
Sent: Tuesday, March 14, 2006 8:16 AM
To: General discussion of project-wide or architectural issues.
Subject: [wtp-dev] Proposal for the hot bug process
Here's what I put together for the hot bug process:
http://www.eclipse.org/webtools/adopters/hot_bug_process.html
Let me know your comments/questions. Thanks.
Jeff Liu
_______________________________________________________________________
Notice: This email message, together with any attachments, may contain
information of BEA Systems, Inc., its subsidiaries
and affiliated
entities, that may be confidential, proprietary, copyrighted
and/or
legally privileged, and is intended solely for the use of the individual
or entity named in this message. If you are not the intended recipient,
and have received this message in error, please immediately return this
by email and then delete it.
_______________________________________________
wtp-dev mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/wtp-dev
_______________________________________________ wtp-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/wtp-dev
