Change in CWS Handling
======================
Summary:
--------
When you are doing binary incompatible changes in your CWS, please mark
those modules 'incompatible' in EIS.
Detailed Description:
---------------------
*Background*: For all current code lines Hamburg RE normally does
compatible master workspace builds (see
http://wiki.services.openoffice.org/wiki/Compatible_Builds ). Code
changes in childworkspaces are by default expected to be compatible.
During integrations we of course are checking whether that's true and
switch to partly incompatible builds if needed, but do not rely on us:
sometimes we miss something. Therefore there always has been a rule to
announce incompatible changes to RE.
Also, whenever several people are working together on a common
childworkspace they have to know when someone does a binary incompatible
change. This of course can be done by email or personal communication,
but sometimes a more formal support would be helpfull.
*Change*: EIS now can handle this information effectivly. On the Edit
page for childworkspaces added modules can be flagged 'incompatible'.
You can see this information in EIS and query it by 'cwsquery
incompatible' (on SRC680 m204, OOF680 m8, or newer milestones). RE
tooling also will use that information. You do not have to care about
dependencies (list of modules which have to be rebuilt from scratch),
just flag the module(s) changed incompatibly. If there are several of
them, mark the lowest one in a depency chain or simply all of them.
*New Policy*: Mark modules where you have done binary incompatible changes.
References:
-----------
What are binary compatible builds? What changes are binary
incompatible? See http://wiki.services.openoffice.org/wiki/Compatible_Builds
About EIS's new features:
http://blogs.sun.com/GullFOSS/entry/eis_incompatible_changes_tinderbox_termite
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
