Hello Lihua,
as Clytie wrote it is more important to know the status of the current
issues as on the oldest issues. In many cases the oldest issues are
complex and many users worked on them in the past, but nobody made a
decision to close it, send it to a developer or ask for more feedback.
The latest issues are better to work on. So as Clytie wrote, please
start with the latest issues first and try to reproduce it on the most
current version (DEV300_m21 and later).
Regards,
Thorsten
Clytie Siddall wrote:
Hello Li Hua :)
On 26/06/2008, at 1:24 PM, Zhu Lihua wrote:
We are about to go over the unconfirmed issues of Calc.
What about the version of OOo used to test? I think lots of issues are
very old.
So they might not exist in the nowaday's version.
And we no need to confirm it in the original versions.
Does it appropriate we use the latest version? For example, DEV300m21.
^^ not 12
Or we use the stable version, such as OOo2.4?
Which one is better?
We can consider 2.4 as the current stable version. So issues reported
against it are still valid. You can check these against the latest build
overall. An issue is also considered FIXED if upgrading to a later
version fixes the problem for the user. (If you have additional time,
you can check it against the latest 2.4 build, but development mainly
takes place in the new version.)
Issues reported against older versions (<2.4) have lower priority. If
they are reported against 2.x, you might also check them in the latest
2.4 build, but we are mostly concerned with making sure our new release
fixes problems. So check first against the latest build overall.
However, this close to the 3.0 release, issues reported against
"current" or 3.x have the highest priority. We want to make sure there
are no major problems, which might block release.
So please check "current" and 3.x issues first, against the latest
available build, and report here any which you think are major problems
(completely disabling a feature, damaging data, causing crashes etc.).
To sum up:
issue reported against check using priority
___________________________________________________
3.x, current 3.0 latest 1
2.4 3.0 latest 2
< 2.4 3.0 latest 3
So, please check against DEV300_m21, and focus on the issues reported
against 3.0/current. Good luck with your bug-squashing. :)
from Clytie
Vietnamese Free Software Translation Team
http://vnoss.net/dokuwiki/doku.php?id=projects:l10n
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
