Difference between revisions of "ChildWorkSpace"
From Apache OpenOffice Wiki
m (→The issue is marked as fixed, but the latest milestone has still has the bug. Why?: typos) |
m (cleanup and spelling) |
||
| Line 1: | Line 1: | ||
== What is a ChildWorkSpace? == | == What is a ChildWorkSpace? == | ||
| − | A concept called <b>ChildWorkSpaces</b> ( | + | A concept called <b>ChildWorkSpaces</b> (CWS) is used to organize changes to [[OpenOffice.org]] into smaller and independent units. |
This page is intended as a first overview for end users. The wiki page "[[CWS]]" provides many more details for advanced contributors. | This page is intended as a first overview for end users. The wiki page "[[CWS]]" provides many more details for advanced contributors. | ||
| Line 9: | Line 9: | ||
OpenOffice.org's code base may be changed as a result of [[Issues]], which can be classified as [[Defect_Report|defect reports]], [[Enhancement_Request|enhancement requests]] or [[Feature_Request|feature requests]]. Issues are managed in a tool called [[Issuezilla | issuezilla]]. | OpenOffice.org's code base may be changed as a result of [[Issues]], which can be classified as [[Defect_Report|defect reports]], [[Enhancement_Request|enhancement requests]] or [[Feature_Request|feature requests]]. Issues are managed in a tool called [[Issuezilla | issuezilla]]. | ||
| − | Related issues get grouped together and are assigned to a | + | Related issues get grouped together and are assigned to a ChildWorkSpace. The resulting code change consists of bug fixes, enhancements and feature implementations that correspond to the list of issues registered for that CWS. |
| − | ChildWorkSpaces are managed in a tool called [[EIS|Environment Information System (EIS)]]: It has all the details about each | + | ChildWorkSpaces are managed in a tool called [[EIS|Environment Information System (EIS)]]: It has all the details about each CWS, e.g. the list of tasks assigned to it, its release target, the first milestone release where it has been integrated, various testing results and the list of code changes. |
== The Process Flow == | == The Process Flow == | ||
| Line 32: | Line 32: | ||
# testing checks for regressions and that the issues are solved | # testing checks for regressions and that the issues are solved | ||
# tested issues are marked as "verified" | # tested issues are marked as "verified" | ||
| − | # testing changes the ChildWorkSpace status to "Approved by QA" | + | # testing changes the ChildWorkSpace status to "Approved by QA" |
| − | + | # the CWS gets nominated either by "[[Program_Management|program management]]" or by testing (depending on the release status of the [[MWS]]) | |
| − | # "[[Release_Engineering|release engineering]]" integrates the code changes into a milestone release | + | # "[[Release_Engineering|release engineering]]" integrates the code changes into the a milestone release |
# the CWS status is changed to "Integrated" | # the CWS status is changed to "Integrated" | ||
# the milestone containing some CWSes is released | # the milestone containing some CWSes is released | ||
| Line 42: | Line 42: | ||
== Frequently Asked Questions == | == Frequently Asked Questions == | ||
| − | === The issue is marked as fixed, but the latest milestone | + | === The issue is marked as fixed, but the latest milestone still has the problem. Why? === |
| − | * if the issue is | + | * if the issue is just marked as FIXED but not CLOSED, then this probably means that the latest milestone doesn't contain the fix yet. Please read the [[ChildWorkSpace#The_Process_Flow|process flow]] section to understand that |
** the list of ''all'' the issues in the CWS has to be solved | ** the list of ''all'' the issues in the CWS has to be solved | ||
** the fixes have to be verified | ** the fixes have to be verified | ||
| Line 52: | Line 52: | ||
=== which milestone release has the issue fixed? === | === which milestone release has the issue fixed? === | ||
| − | * the [[EIS]] | + | * the [[EIS|EIS tool]] provides details like this for a CWS. You can [http://eis.services.openoffice.org/EIS2/cws.InfoForTask find that EIS entry] by entering the issue number. |
* the closing comment of a fixed issue is supposed to mention the milestone | * the closing comment of a fixed issue is supposed to mention the milestone | ||
* the milestone's release notes contains an extensive list of resolved issues | * the milestone's release notes contains an extensive list of resolved issues | ||
| − | |||
[[Category:Development]] | [[Category:Development]] | ||
[[Category:CWS]] | [[Category:CWS]] | ||
Revision as of 09:57, 1 December 2008
Contents
What is a ChildWorkSpace?
A concept called ChildWorkSpaces (CWS) is used to organize changes to OpenOffice.org into smaller and independent units.
This page is intended as a first overview for end users. The wiki page "CWS" provides many more details for advanced contributors.
How does it relate to Issues?
OpenOffice.org's code base may be changed as a result of Issues, which can be classified as defect reports, enhancement requests or feature requests. Issues are managed in a tool called issuezilla.
Related issues get grouped together and are assigned to a ChildWorkSpace. The resulting code change consists of bug fixes, enhancements and feature implementations that correspond to the list of issues registered for that CWS.
ChildWorkSpaces are managed in a tool called Environment Information System (EIS): It has all the details about each CWS, e.g. the list of tasks assigned to it, its release target, the first milestone release where it has been integrated, various testing results and the list of code changes.
The Process Flow
The relationship between an issue, a CWS and a release is described in this simplified process flow:
- someone finds a problem or has an enhancement idea
- the problem or the idea shouldn't be known in issuezilla yet
- a new issue is submitted
- the issue is confirmed/tested by testers and/or developers
- the issue is marked as "confirmed"
- development accepts an issue by marking it as "new"
- development creates a ChildWorkSpace
- development assigns some issues to the CWS's task list
- development solves the issue and tests the solution
- development commits the code changes into the CWS's code base
- development marks the issue as "fixed"
- development checks that the whole CWS works as expected
- development changes the CWS status to "Ready for QA"
- development reassigns the issues to testing
- testing checks for regressions and that the issues are solved
- tested issues are marked as "verified"
- testing changes the ChildWorkSpace status to "Approved by QA"
- the CWS gets nominated either by "program management" or by testing (depending on the release status of the MWS)
- "release engineering" integrates the code changes into the a milestone release
- the CWS status is changed to "Integrated"
- the milestone containing some CWSes is released
- testing checks the issues again on the released version
- testing marks the issues as "closed"
Frequently Asked Questions
The issue is marked as fixed, but the latest milestone still has the problem. Why?
- if the issue is just marked as FIXED but not CLOSED, then this probably means that the latest milestone doesn't contain the fix yet. Please read the process flow section to understand that
- the list of all the issues in the CWS has to be solved
- the fixes have to be verified
- the CWS must be integrated
- the milestone has to be released
- if the issue is marked as closed and fixed but the milestone mentioned in the closing comment still has the bug then
- please reopen the issue and provide exact details on how to reproduce the problem
which milestone release has the issue fixed?
- the EIS tool provides details like this for a CWS. You can find that EIS entry by entering the issue number.
- the closing comment of a fixed issue is supposed to mention the milestone
- the milestone's release notes contains an extensive list of resolved issues
