Configuration Management, Version Control, and Baselining - Suggestions needed

[jpvonoy]

I have recently released a product and I want to create a major baseline of my design to represent the as-released Version 1.0 design of the product. 

Going forward, I want to start making updates and modifications to the design for either a minor baseline (version 1.1, 1.2, etc.) or possibly go right to releasing the Version 2.0 of the product.

What are some ways I can achieve this minor and major baselining in Fusion 360?

This may or may not be important to the answers, but my product consists of around 400 components that are spread across 4 Fusion designs. There are also drawings of every part that are released with each new product release.

Thanks for your suggestions.

[jodom4 · Accepted solution]

Hey jpvonoy,

We've got a new feature we're working on that might be useful. We'll be in touch with a feature flag and some internal support to get you going with it.

[Anonymous]

Has this new version control feature been released yet?

I'd like to be able to use it too. Thanks

[Anonymous]

@jodom4 I have been pushing the use of Fusion 360 at our company for some time now.  We absolutely would need proper version control to implement F360.  Has any progress been made on this front?  Thanks!