This page section is available in English.
QATrack is the OpenOffice.org Communitys build management system. It provides the primary information spot for builds and supports the OpenOffice.org Community in all steps of the QA and release processes.
If you need help with your account, update account details, or need answers to your questions, please contact one of the following.
Your first tip if you have questions about how to use QATrack, contact the following mailing list:
dev@qa.openoffice.org
If you need technical changes made to your account, please contact one of the following administrators. If you want to have a language added to your account, you can also contact that language's QA Lead.
| Name | Account Name |
|---|---|
| Per Eriksson | pereriksson |
| Joost Andrae | ja |
Note: Add @openoffice.org to the account name to get the full email address to the person.
While all information in QATrack is publicly available without the need to log in, having an account gives you the ability to change user interface language, and gain more access are you get more involved.
Your can get an OpenOffice.org account here:
Get an OpenOffice.org Account
Send an e-mail to dev@qa.openoffice.org to request permissions to the QATrack system. Please specify the languages that you would like to get access to.
Read more about roles below.
When you have the permissions that you need, you are ready to log in to QATrack.
If you have another primary language than English, you might be interested in any of the languages that QATrack is localized in. Click Account Preferences in the upper right corner of the header, and change your interface language.
This section provides this help information.
This section provides credits for the QATrack system.
Shows information about your QATrack account, and provdies the ability to change the interface language.
Press this link to log out of QATrack.
The first page serves as a dashboard and gives you an overview of the latest builds that are interested for you.
It displays your languages' latest builds on the left with the Int Id, Version, Platform and Status of each build.
In the middle latest English (United States) builds are displayed with the Int Id, Version, Platform and Status of each build.
You can click on any builds Int Id to get to the build's page.
On the right messages posted by the portal's administrators are shown with the latest message first. It also gives you the latest news from the RSS feed.
For more information about builds, see Show_Builds.
The View Status page provides an advanced search feature to query the database for the status of a specific version, language, platform, status and more.
The field Version is required to limit the preassure on the QATrack system and must contain at least 3 characters, e.g 2.4.
The field Available for last specifies the days since the build was added (provided) to the system.
If a field is not filled in, all possible values are implied.
The search engine provides two views, Overview view, and Detailed View.
The Overview view displays an overview of all the builds returned by the result. Each build has the color associated with its current status, and an initial letter of its current status.
The Detailed View displayes a detailed view of the builds returned by the result. Each build has the color associated with its current status, and displayed the version of the build. Each build in this view also has an advanced tooltip displaying the builds Build Id, Version, Status, Responsible, Created and Filename fields of the build.
The search result URL can easily be copied and sent to another individual as the URL contains the search parameters specified.
This page allows users to provide builds to the QATrack build management system.
The builds that you can submit here largely dipends on the global role and languages that are associated by your account.
Administrators and Build Providers can submit builds for all languages. Other users can only submit builds for the languages that are associated with your account.
The process is divided into 3 steps defined below.
Tip: You can click on a language name to select the language. You do not have to click on the checkbox.
The builds are added in accordance with your request. A Build Submission Report is displayed which you can save as a receipt.
An email for each build is sent to all users which are associated with that build's language.
An entry is added to the RSS feed with all the builds added.
This section is managed by system administrators. Users can view users sharing the same languages as themselves.
QATrack is built upon a system of roles, where some users have more access than others. Rights exist on a global level, as well as on a language level. The language roles are identical in terms of access, and only exist for organisational purposes. Global roles and language roles can be combined to create the right level of access for the user.
| Code | Name | Meaning |
|---|---|---|
| ADM | Administrator | Has access to the system's all resoures. |
| BPR | Build Provider | Has access to provide builds for all languages. |
This section provides the ability to manage the languages accepted by QATrack. Languages not in this list are not accepted by the QATrack build management system.
Only QATrack system adaministrators can change this section. If you would like things changes, contact a system administrator in the Help section.
| Code | Name | Meaning |
|---|---|---|
| QAL | QA-Lead | Has access to the language's all resources. |
| QA | QA | Has access to the language's all resources. |
For each build displayed in QATrack, the Int Id for that build provides a link to the build page of that build.
The build page can be updated by an account which is associated with the build's language, or any administrators.
This section provides basic information about the build.
This section allows adding or modifying the TCM Report URI.
This section provids a field for specifying the person responsible for the build.
This section describes the current status with the fields Status, Since and Until. The two latter fields are related to the current status.
The following table describe the different statuses and their meanings.
| Status Code | Meaning | |
|---|---|---|
| APPROVED | The build has after QA testing been approved for distribution. | |
| DISTRIBUTED | The build has been distributed technically through the mirror networks. | |
| INQA | The build is undergoing QA testing. | |
| NOTIFIED | The users have been notified about the availability of the new build. | |
| PUBLISHED | The build has been published on the website. | |
| REJECTED | The build has been disapproved after QA testing. | |
| UNAVAILABLE | The build has somewhere in the process got a broken URI. | |
| UNTESTED | The build has not started QA testing. | |
For each change made to the build on this page (including adding an IssueZilla issue) you can comment the change. Add the comment under this section to add a message to the build comment log.
Comments can be added to the build without changing anything else.
This is the build's comment log, displaying all comments added by users. Comments are displayed with the first comment first, the last comment added displayed last.
This section, as the comment log, displayes the issues associated with this build. Each issue shows the basic information about the issue, with a hyperlink to that issue's page in IssueZilla on the OpenOffice.org website.
Enter an issue number here and click Save Changes to add an issue to this build. Added issues can be removed at any time by checking the issue's Remove checkbox and click Save Changes.
The syntax for the build names has been decided on the releases@www.openoffice.org mailing list. QATrack conforms to the specification that can be found here.
