Branching & Merging Consistency in LabVIEW

[Ajay_MV]

Hi All,

Good day to you! 

I am in middle of bringing up my LabVIEW (LV) based software product into SVN repo.  Before branching I'm stuch with a big question "Will branching and merging be a cool job inLabVIEW?".  

In my experience, I can say that LV merging is not that cool.  If the changes is minimal and VI size is small, LV merge is acceptable to use.  In case of numerous changes (lot of deletions and additions in block diagram(BD), changes in FP), LV can not withstand (loading of differences takes too long, merging confuses if the BD is huge enough, and many times LV run out of memory and crashes).  In such case, how can a product be built which has consistent release (tags), bug fixes of old release, new feature addition (branch) and integration of bug fixes and new features into trunk (merge)?  Is it at all possible with LV graphical paradigm?  What is the best practice you would suggest?

Thanks,

Ajay.

[mikeporter]

SVN has no impact (plus or minus) on LabVIEW's ability to merge. SVN simply provides a way to call the merge function that LabVIEW procides.

Mike...