Andrew Jensen wrote:
Frank I understand your point about not releasing every fix possible
in every maintenance release as a form
of risk management. I also did a quick query off IssueZilla finding
108 defects marked for target of 2.0.2
that have been changed to resolved in the last 369 days ( excluding,
as best I could, those dealing solely
with documentation [203 if I query everything]). Also 9 enhancements?
So, of course you guys aren't just loafing.
Further, I suppose it is reasonable that a person should make note
of the fact that a defect marked as resolved but not given a target
milestone is not in the queue to be
released.
Some releases have a very specific reason or focus. Version 2.0 was
released knowing full well that certain issues still existed so they
made the release with plans on what to fix immediatly, nothing more and
nothing less. You fix these and then we release. If you are a tester and
you are testing something else, then you are probably in trouble.
Now, that said.... I wonder what would not have been released if they
had taken the time to verify some of the other stuff...
--
Andrew Pitonyak
My Macro Document: http://www.pitonyak.org/AndrewMacro.odt
My Book: http://www.hentzenwerke.com/catalog/oome.htm
Info: http://www.pitonyak.org/oo.php
See Also: http://documentation.openoffice.org/HOW_TO/index.html
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
