On Mon, Feb 18, 2013 at 8:59 PM, jdaniel.alvaro <[email protected]> wrote: > Thank you rob, > > Other question, What do you mean "fixed in trunk? >
Good question! Think of a tree, with a main trunk and many branches. The code for OpenOffice is stored in a repository called a "version control system". The specific product we use is called "Apache Subversion". You can see the code here: https://svn.apache.org/repos/asf/openoffice/trunk/main/ When we work on a new major version of OpenOffice, like 4.0, the programmers do the following: 1) New features, when they are complete, are placed into the "trunk" of the repository. (We call that "checking in code into the trunk"). The trunk is where the stable code goes. It is where we do most of our testing. When we release AOO 4.0 we release based on what is in the trunk. 2) Developers can also create "branches". This is where "work-in-progress" features live, features that are not stable or complete. This allows developers to work in isolation on their features without causing conflict with other developers. The accessibility work for AOO 4.0 is in a branch right now. The side panel UI is also in a branch. You can see all of our branches here: https://svn.apache.org/repos/asf/openoffice/branches 3) When a developer completes their work in a branch, then that code is "merged" into the trunk. 4) When we say something is "fixed in the trunk" we mean the code that fixed the bug was checked into the trunk. That means you can see the fixed code when you test a trunk build. 5) If you look carefully at our snapshot builds, you can see that some of them are labeled "branch". All the others that are not labeled branch are trunk builds: http://ci.apache.org/projects/openoffice/index.html Regards, -Rob > On Mon, Feb 18, 2013 at 7:42 PM, Rob Weir <[email protected]> wrote: > >> On Mon, Feb 18, 2013 at 8:02 PM, jdaniel.alvaro >> <[email protected]> wrote: >> > when I close the bug with "CLOSED" I have other options as in the image. >> > >> > http://imagebin.org/247224 >> > What option I need to choose with "CLOSED"? >> > >> >> If you tested the build and verified that the bug was fixed, then >> CLOSED/FIXED is the right choice. >> >> If you test and the bug still occurs, then you do a REOPEN. >> >> Regards, >> >> -Rob >> >> > >> > On Mon, Feb 18, 2013 at 6:22 PM, Rob Weir <[email protected]> wrote: >> > >> >> On Mon, Feb 18, 2013 at 7:19 PM, jdaniel.alvaro >> >> <[email protected]> wrote: >> >> > Yes, but if i'm not the QA Contact I can't change the status, to >> >> > "Verified" or "Closed" and I see that there are many old bugs and i >> >> want >> >> > to close it, I can't do it because i'm not the QA contact, how can do >> >> this? >> >> >> >> Do you get an error message when you try to change the status to >> >> "Verified" or "Closed"? >> >> >> >> The QA Contact field is only for tracking. It does not control >> >> permissions in Bugzilla. >> >> >> >> -Rob >> >> >>
