Hi,
On 10.07.2012 03:51, Li Feng Wang wrote:
Very useful to unify QA work,
Suggest to add tag when file or verify defects, like
[MemoryLeak]:Memory Leak defect, need verify via long time running.
[Dev]: Open by developer, and may can't verify from user view.
[Crash]: Crash defect
[Regression]:Regression defect
[Lost]:Defect about data lost .etc
marking/tagging issues correspondingly is very useful.
For above mentioned "Crash", "Regression" and "Lost" we already have the
corresponding keywords "crash", "regression" and "data_lost".
I am not sure, but may be we should thought about having only one way to
mark/tag issues.
Best regards, Oliver.
2012/7/10 Ji Yan <[email protected]>
2012/7/10 Regina Henschel <[email protected]>
Hi all,
in times with CWS and EIS there was a description of Issues lifecyle,
http://www.openoffice.org/qa/**ooQAReloaded/Docs/QA-Reloaded-**
IssueHandlingOverview.html<
http://www.openoffice.org/qa/ooQAReloaded/Docs/QA-Reloaded-IssueHandlingOverview.html
.
Some parts are lost and others totally outdated.
But I think, that such an information is useful and start a draft in
http://wiki.services.**openoffice.org/wiki/User:**Regina/MYDrafts4<
http://wiki.services.openoffice.org/wiki/User:Regina/MYDrafts4>
Do you agree to provide such information?
If yes, where to put it?
If yes, please improve the text.
Kind regards
Regina
Your document is very helpful. Looked in bugzilla guide I find Bugzilla has
issue life cycle definition [1], this diagram show the life cycle more
clearly
IMHO we should have more detail document to help user file bug, may I add
my thought on how to file bug in your page?
[1] https://issues.apache.org/ooo/docs/en/html/lifecycle.html
--
Thanks & Best Regards, Yan Ji
