In case the build breaks on a master milestone (and we notive that) it
is common practise that RE fixes such problems on the master before the
milestone gets announced as 'ready for use'.
You may query EIS for childworkspaces with status 'fixed on master' or
named '<mws><milestone>masterfix' to see how often that happens.
Rüdiger
James Mckenzie wrote:
Pavel:
Thank you. Is it usual to fix a problem directly on the master?
James McKenzie
-----Original Message-----
From: Pavel Janík <[EMAIL PROTECTED]>
Sent: Apr 13, 2007 11:05 PM
To: [email protected]
Subject: Re: [porting-dev] Re: [porting-cvs] CVS update:
/porting/sal/rtl/source/
Hi James,
It would be nice to know why you made this change sinch the cws
associated with it
did not go through.
as you can see in EIS, this issue (#i76245#) is associated with cws
src680m209masterfix thus it was fixed directly on master and it will
be included in SRC680_m209.
--
Pavel Janík
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
