For those using Lifecycle based revisioning, what is the initial revision?

[avillanueva]

I believe in cases where you have prototype revisioning (numeric) that transitions to production revisioning (MilSpec), what is your initial revision? Do you start with a dash revision or the numeric? We are currently using just the latter and have a seed value of dash. The question is what happens if we introduce lifecycle based revision series for a prototype process. My assumption is that everything would start out as a prototype (numeric) until that production release where is would go to our dash, right? Or is it better to start with dash as a seed for numerics and then do to A as the start of production release. Looking to hear from people who do this currently.

[sdrzewiczewski]

We use numeric then alpha. Some of our older products used a scheme of (-,A,B,C,...)

What we decided to do was no longer use '-' as a rev, but in order to switch versioning schemes the versions in the current scheme must be in the target scheme. So we added '-' to the front of the numeric scheme and set as legacy='true'. This allowed objects that already had '-' to switch versioning series, but any new item started at '1' instead of '-'

attached is our filebased series.