Hi Drew,
Andrew Jensen schrieb:
HI,
I have a question, maybe a few, regarding how to tell when a fix for a
particular issue has been integrated into a given build.
Perhaps the easiest way, for me, to explain myself is to use the
current issue I am looking at.
Issue 69541
The last entry shows that it has been verified and that it was fixed
in CWS dba23a.
I have gone ahead and tested this using 2.3m_210 downloaded from an
OOo mirror and 2.3m_211 downloaded from linux.cz under Win XP - in
both cases the test fails for base files connecting to XLS or ODS
files.
Before I reopened the issue I wanted to make sure that this was not
perhaps just because the code had not integrated into the build yet. I
went to look at the EIS entry for the CWS dba23a.
I see there that it was created at milestone m_200, that the current
milestone is m_206 and that the integration milestone is EMPTY.
dba23a is indeed not yet integrated into the main codeline. That's why
you can see and verify the fixes only on the Child Workspace (CWS) yet.
Thus the empty integration milestone.
OK - but then I think, well the current milestone is not still 206 it is
210 - so: Is that entry for current milestone simply the milestone at
which the last edit was made for this CWS?
The current milestone m206 of the CWS means that the CWS has been
synchronized with milestone m206 from the main codeline, the Master
Workspace (MWS). So the CWS now contains m206 as a basis plus its changes.
I look a little deeper to the Tinderbox entry and see that there are
build problems for three separate build environments Fedora, Mac OSX
and Linux all using gcc. Fine, but I am using a build created with MS
VC++ so: Does the fact that the builds are failing ( or not
appropriate in one instance since there have been check-ins ) under
these other environments mean that these changes would not have been
included in the Windows build also?
It would seem simple to say, EMPTY slot for integration
milestone...but, the issue says it has been VERIFIED as FIXED - so it
must have been built at least once by someone and tested?
It has been tested on the CWS. As soon as the CWS gets integrated into
the MWS the issue can be verified there and then closed.
Thanks
Drew
Regards,
Joerg
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
