To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=54567





------- Additional comments from [EMAIL PROTECTED] Mon Feb 19 13:32:52 +0000 
2007 -------
Although I tend to be polite, I must object the target milestone 3.0.

This bug annoys users for year and half, it is P2-grade bug (data loss). Taking
in account, that the bug was uncovered as soon as during 2.0 BETA stage, should
been fixed even BEFORE 2.0. It's bad enough that it made it to the stable 2.0,
bad enough it was not fixed for 2.0.1, 2.0.2, 2.0.3, 2.0.4, 2.1 and just pushed
to 2.x. Pushing it towards next major is really bad. What will be done then?
Pushed to 3.x and then to 4.0?

Cite: "Issues with this priority must be fixed before the target release (see
Target milestone), which usually is the next major release, and should be dealt
with as soon as possible. Not fixing them for the target release is not 
acceptable."

Cite: "# User data is corrupted in an easy-to-encounter way;
e.g. saving a document corrupts the resulting file and renders it unusable
# Crashs or freezes during normal operations of the application"


Pushing the bugs does not resolve them, nor it makes users happy. I'd rather
spend more time waiting for next release to see the bugs actually fixed, than
watching bazillions of releases with no visible progress on serious bugs. I'm
happy for tiny tweaks here and there, but this dosen't make the major bugs
dissappear. Could anything annoy users even more than severe, well-known,
years-lasting bug?

---------------------------------------------------------------------
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]

Reply via email to