Kohei Yoshida wrote:
But considering the immediate benefit of these two patches that a
large number of users will enjoy, perhaps a slight breakage in
functionality (not saving the state in the document) which the
majority of users will not even notice may be warranted?
I do have a more in-depth idea about some QA issues regarding this
(general QA issues, not related to these patches or sc project). Which
is the best mailing list to post, though?
I fear way too many patches rest somewhere, because of lacking QA
approval. On the other side, many patches/ hacks are not up to the
expectations, and one major impediment is that far too few people have
tested them (including those who need them *AND* those who do NOT like
them).
I wish to expand on this issue and offer an alternative system. It is
NOT intended to replace the *QA* in any means, it is to offer better
testing before final implementation, therefore better specification
development, more user input on various issues and faster deployment to
the end-users of various patches.
Kind regards,
Leonard Mada
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
