Hi there!
Everyone using a mercurial based CWS MUST enter the new milestone in EIS manually after rebasing the CWS to a new milestone using mercurial commandline or gui tools.
For SVN and CVS Childworkspaces the "cws rebase" Kommand stored the information about a new milestone in EIS. Mercurial based CWSs are updated to a newer milestone using mercurial tools only. These do not know about EIS at all. Thus in order to not break processes which depend on the correct milestone version information in EIS like buildbots or automated tests do for example a developer MUST update milestone information in EIS manually after using mercurial tools to update the source code to the new milestone.
The Milestone and the MasterWorkspace are two separate Fields on the CWS EditPage in EIS. The Milestone field MUST only contain the milestone (eg. "m53") and MUST NOT contain masterworkspacename+milestone (eg. not "DEV300m53").
Kind regards, Bernd Eilers --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
