I have some questions regarding the use of release levels. Currently,
everything we have is WIP. We are looking at a way to check parts into
Commonspace before we are ready to release them. Currently, we keep
things in our WS until ready to implement and then we check in.
Recently, we have had some projects draw out for extended periods of
time (1 year) and would like some way to check in without over writing
the current files until it's time to implement.
My first thought was to create a branch. Initially, this seemed like
the perfect method...I could revise my parts and check them into a
different branch and then merge when it was time to implement.
BUT....my first attempt to do this failed. I have a existing family
table part and added an instance. I also created some drawings that did
not previously exist. Ilink will not allow you to set the branch on
the "instance" or drawing that doesn't already exist in CS. So much
for that theory.
So, I am investigating using release levels but am a little fuzzy on the
infrastructure. First, do you promote/demote in CS or in a WS? Second,
when you promote/demote, are you actually "moving" that part or are you
creating a copy? If I have a part that is currently being used and I
need to make a revision, what are the general steps....I'm thinking we
would only have 2 levels (production and prototype).
Or, is there another method out there that people are using to
accomplish this? Thanks in advance for any insight.
Amy Cashen
Engineer II
The Delfield Company
Manitowoc Foodservice
T 800.733.8821 x12634 | F 989.773.1588
Integrity, Commitment to Stakeholders, and Passion for Excellence.
