On 09/07/2008, at 12:08 PM, Zhu Lihua wrote:

Hi Thorsten,

Thanks for the explaination.

So it seems OOH680_mX is a Code base name, and OOo2.4 is a Version Name. Is that right?
But in the issuetrack, the version field contents both of the names.
So I think, actually, they are equally used in our work. Is that so?

Yes. We (the OpenOffice.org Project) tend to use the build names, because they are more specific. You have many different development builds for a single release. However, OpenOffice.org users tend to identify the program by a version number. That's why you see both references in the Issue Tracker.

Pavel's excellent slideshow also helps explain the release process. [1]

The way I tried to explain the codelines to my team was:

xxx680 — main codeline

DEVxxx — development builds towards a particular release

BExxxx — beta builds

These codelines run parallel, but they do different jobs. The main codeline always continues, but it branches off to test features and changes for each release. Beta builds are for wider testing. It's important to remind users that the DEV and BE builds are not stable versions: they are primarily for testing.

However, that makes it difficult for us when a user reports an issue. If they do remember to tell us which version they're using, even if they say "OpenOffice.org 3.0b", we're left wondering, "Which build?" But at least we have some information. :)


BTW, I'll participate in the orgnization of the IRC meet. Please let me know when you decide
to start a meeting, maybe I need some preparation on it.

I have no much experience in IRC. But I think after 1 or 2 meetings, we could do better.

I've registered as "redflagzhulihua" in #qa.openoffice.org.

I look forward to seeing you there. Unfortunately, I am going to be unavailable for a week or two, but I hope to be back after that. :)

from Clytie

Vietnamese Free Software Translation Team
http://vnoss.net/dokuwiki/doku.php?id=projects:l10n

[1] http://blog.janik.cz/files/OOoCon2006/img0.html

Attachment: PGP.sig
Description: This is a digitally signed message part

Reply via email to