Hi Muthu,

On Friday, 2007-06-01 22:16:43 +0530, Muthu Subramanian wrote:

> It would take me ages to resync msba01 to src680 (since I have a very slow
> internet connection).
> But, since i56202 is a small one - is it really necessary?

Yes, for the following reasons:

1. To be sure the change behaves as intended, QA has to test the change
   on the release branch the change is intended for.

2. To be sure the change integrates flawlessly the CWS has to be
   resynced to one of the latest milestones available on the release
   branch. Otherwise chances for merge conflicts to occur raise with
   every milestone in between.

> If it is then re-cws'ing (download source, create new cws, commit) is much
> faster for me. (or if somebody helps me resync it!)
> Btw, can I re-use msba01 in case I decide (or rather get no-option than) to
> 're-cws'?

Not sure if I got that right, but your options are either

- Resync msba01 to SRC680 m214 (or later), maybe not such a good option,
  given that OOF680 and SRC680 already differ quite a bit, and there
  remains a chance that due to typos, broken connection or whatever you
  end up with an inconsistent state of your build environment.

- Set msba01 in EIS to status deleted and do a
  cvs diff -up -rCWS_OOF680_MSBA01_ANCHOR -rcws_oof680_msba01 >patchfile
  (yes, capitalization in the revision tags is intended), create a new
  CWS, e.g. msba02, based on SRC680 m214 and apply the patchfile.

> I thought owner was set automatically! Sorry, will set it correctly.

Usually it is, maybe it wasn't because that was the first CWS you
created and your account wasn't listed yet.

  Eike

-- 
 OOo/SO Calc core developer. Number formatter stricken i18n transpositionizer.
 OpenOffice.org Engineering at Sun: http://blogs.sun.com/GullFOSS
 Please don't send personal mail to this [EMAIL PROTECTED] account, which I use 
for
 mailing lists only and don't read from outside Sun. Thanks.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to