To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=113866
User fs changed the following:
What |Old value |New value
================================================================================
CC|'fma,mba,mh,pl,sb' |'fma,fs,mba,mh,pl,sb'
--------------------------------------------------------------------------------
------- Additional comments from [email protected] Mon Dec 6 14:54:37 +0000
2010 -------
I don't really think that makes sense (what about targets like "extension
release X.Y", which should not be changed at all?) ...
Plus, I don't see the benefit. *After* a bug has been fixed, or maybe *after*
the respective CWS has been integrated - what is the target on an issue good
for? What information can you obtain from it? The release the bug fix went in?
Well, that can be obtained from EIS (issue is part of a CWS => CWS has been
integrated into release). Other than that? Don't know.
Seriously, I think that a target expresses an intention where the bug fix should
appear. After the bug fix manifested in a release, or even after it is in MWS,
the target at the issue becomes rather meaningless.
So, my gut feeling is that whoever uses the issue target in such a phase is
simply evaluating the wrong data (feel free to prove me wrong on this). We
should not support this by adding complex and error-prone extra functionality to
EIS, but by providing a means to evaluate the proper data.
---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
