Hello Peter,
if there is a remark "fixed in src680/dr32" or "verified in cws dr32" then this means that there is a child workspace (abbreviation: cws) named "dr32" on which the developer has fixed his bugs. BIFF5 is the internal name of the storage file format type of Excel5 and BIFF8 is the internal storage name for Excel97 files. If you want to track when a bug has been fixed within a child workspace and when such a cws has been set to "ready4qa" then you could have a look at the environment information system (EIS) at http://eis.services.openoffice.org
Most bugs within child workspaces are QA'ed by Sun QA. Some CWS builds are uploaded to http://ooomisc.services.openoffice.org/pub/OpenOffice.org/cws/upload/
but testing child workspaces will need more than using that cws. Sun QA is currently acting as gatekeeper for child workspaces because most of the OpenOffice.org builds are done by Sun and approving a child workspace for integration needs some automated tests to be done besides that all issues have been verified. If a cws has been approved by QA then often there is a source review before this cws gets approval for integration. If a cws has approval (nominated) then this cws gets into a queue of several cws'es. When the cws has been integrated then all issues need to be verified again on the master build before they can be closed.
Another bug said it was fixed in 680m74s1 and I guess that is different than my 1.9.74.
There are master workspaces and there are step builds. Master builds are usually done every week and they're available via CVS. Sun regularily provides developer snapshots which are uploaded to the mirrors. Step builds are rare because they are intermediate builds if there's time to do an additional build within a week.
Another issue says "fixed in CWS extras17." Can I tell from that when something will be fixed.
No. If there is an entry "fixed in CWS XYZ" then you cannot assume when it will be integrated. If you look at the EIS application then there is the estimated due date but the integration date is not known at this time.
Also, what do all the periods mean in an issue.
As no status change can be done without a comment every developer includes a period if he wants to change the status.
If there is a document that explains all of this, I will gladly read it, I am just not sure where to start looking.
That would be worthy
Kind regards, Joost
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
