Main > Knowledge Base > Best practices > Creating and changing metadata objects > Application version control > General information about application releases > Best practices > Creating and changing metadata objects > Application version control > General information about application releases > Best practices > Creating and changing metadata objects > Application version control > General information about application releases

General information about application releases

This article describes the standards that apply to configuration releases. All of the listed recommendations are mandatory unless noted otherwise.

1. Configuration releases have versions and revisions.

2. A version includes bug fixes and minor improvements. A new version upgrades the previous one while preserving its data.

3. A revision includes considerable changes in the accounting structure, which require data conversion. The need for data conversion is often (but not always) a formal reason to increment the revision number. We recommended that new revisions provide automatic data migration during the upgrade. If for any reason this is impossible, describe the migration procedure (how to start, how to migrate opening balances, and so on) in the documentation.

Next page: Version and revision numbering.





© 1C LLC. All rights reserved
1C Company respects the privacy of our customers and visitors
to our Web-site.