Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.
Gerhard Fiedler wrote:
>
> I can see what you're doing here, but I probably would use a tag IFS_711_A
> for the /complete/ set of files of release IFS_711 for customer A. I'm not
> a fan of partial tagging...
We have been discussing that, and that would have to negative sideeffects:
1) it would be impossible to review/list those files specially
modified for costumer 'A'
2) When IFS_712 is released, I'd have some tagging problems,
detecting where to place the IFS_712_A tag. I cant use IFS_711A, as it's
definately wrong on base files (those not modified for that costumer).
But I could update to stickytag IFS_712 and then tag all files as
IFS_712_A, then stickytag to Costumer_A (removing all other files on the
sandbox) and move IFS_712_A on these files. then I should have a
useable combination of IFS_712 and Costumer_A so we we can start our
automated build.
This is a bit akward though, as we are talking 10 modules containing 25
to 890 files each, in all 1825 files on a rough count.
That would indeed massage the CVSNT server on each automated build. :-)
Best regards Henrik