Hi Justin, > If I've come across a bug in OOo2 Base 680m77, and find an existing bug > for it in IZ (#42033) marked as RESOLVED/FIXED (680m75), does that means > it should be fixed already for m77 and I need to report it's still > broken, or not? > > Not quite sure on the best way to proceed in future.
If an issue is marked as FIXED, then it just means that the developer checked in the fix - it doesn't imply the fix is available in a snapshot. Without going into detail: Developers work on branches only (so-called CWS [1]), while the snapshot is made from cvs-HEAD. FIXED means the fix made it onto a branch only. If you want to see the status of the branch where an issue is fixed, go to eis.services.openoffice.org, menu "Child Workspaces"/"Search", and search for the issue. This gives you an idea of the status of the child workspace, and also into which milestone it is integrated. If you don't want that much detail, look for CLOSED: According to "A bug's lifetime", described at http://qa.openoffice.org/issue_handling/, an issue is CLOSED when it's verified that the fix made it into the developer snapshots ([2]) (the so-called "master"). So if the issue is CLOSED it means it should be fixed in the master, if it is still RESOLVED, it is either not yet integrated, or not yet verified. Ciao Frank, who certainly is going to describe this in a public linkable place, some time .... [1] go to tools.openoffice.org if you want to learn more about the concept [2]http://qa.openoffice.org/issue_handling/workflowcharts/taskhandling_workflow_issuetracker_fix_close.html --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
