Guido Ostkamp wrote:
Hello Caio Tiago,
[cut]
Yes, that's clear to me. However I did expect that OOF680_m1, after
calling it officially a "beta" is complete though it is not an "RC" yet.
The issue was fixed there, but that CWS was not integrated to OOF680_m1.
This clarifies things a bit. I consider this bug a release critical issue.
Can we expect that this CWS will be integrated before release of 2.2?
I have the same concerns. I mean, beta should be used for testing the
final feature/fixes, so you can discover if something else has been
"worsened" in the process (regressions).
I have a bug that prevents me to test it in my office for daily work
(yes, I've a daily backup also of my data ;)).
Is issue 71484 and has not been integrated in m1 (happily, I see now
that has been in m2).
This prevents me from use m1 for testing, and if we will have CWS
integrated short before the final release, very short time will be left
for testing.
My idea is that there should be development versions of OOo, like m197,
m198, etc., then when we want to go for beta, all the CWS should be
integrated so people can test if the fix are properly made and if they
don't have regressions. If not, I don't understand why call m1 "beta".
In addition, having bugs that in Issuezilla are flagged as FIXED but
that are not integrated can be confusing. If someone tests the last
build and find that the bug is still there, will reopen or report it
again (as happened to me with the above mentioned bug).
Just my opinion
Marco Menardi
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
