You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As far as I'm aware, there is no versioning convention used in the VPIC source apart from distinguishing between "v4" and the master branch.
Can a VPIC versioning convention be adopted? The big differences are between v407 and master, but there may also be slight version differences between releases which may result in different output. Not having a versioning convention means an ad-hoc approach to versioning deployments, such as timestamps.
The text was updated successfully, but these errors were encountered:
As far as I'm aware, there is no versioning convention used in the VPIC source apart from distinguishing between "v4" and the master branch.
Can a VPIC versioning convention be adopted? The big differences are between v407 and master, but there may also be slight version differences between releases which may result in different output. Not having a versioning convention means an ad-hoc approach to versioning deployments, such as timestamps.
The text was updated successfully, but these errors were encountered: