- Version and revision numbering
- General information about application releases
- Filling configuration properties with the release details
Version and revision numbering
This article describes the standards that apply to version and revision numbering. All of the listed recommendations are mandatory unless noted otherwise.
1. The number of the next configuration revision is the next integer number after the previous revision number. Usually a revision number is followed by a subrevision number, separated by a period, for example: revision 1.5, revision 1.6, and so on. New configuration releases start from revision 1.0.
2. All versions of a subrevision (including alpha, beta, prerelease, and release versions) are numbered in the same manner. Version numbering starts with 1.
3. The revision number, subrevision number, and version number are combined in the full configuration version number. Specify it in the Version property of your configuration using the following format:
{R|RR}.{S|SS}.{V|VV}.{B|BB}
where:
R is the revision number (1 or more digits);
S is the subrevision number (1 or more digits);
V is the version number (1 or more digits);
B is the build number (1 or more digits).
Example: 1.6.4.7 stands for revision 1.6, version 4, build 7.
See also: 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.
See also: Version and revision numbering.
Filling configuration properties with the release details
1. Synonym.
The official configuration name, which is printed on the product box, as well as in the documentation, price list, advertising, informational and tutorial materials. The revision number follows the configuration name.
Example: AccountingSuite 1.1.
2. Name.
The name is generated based on the synonym according to the name generation rules. The "revision" word, and revision and subrevision numbers are omitted.
Example: AccountingSuite.
3. Brief Information.
The brief information is identical to the synonym.
4. Detailed Information.
The detailed information is identical to the synonym.
5. Logo.
The configuration logo.
6. Splash.
A 305x110 pixels image.
7. Copyright.
A string of the following format: Copyright (c) <developer name>, XXXX-XXXX. All rights reserved.
XXXX-XXXX stand for the years of configuration development.
Example: Copyright (c) 1C-Soft LLC, 2008-2017. All rights reserved.
8. Vendor information address.
The vendor website address.
9. Configuration information address.
The product website address.
10. Vendor.
The vendor name.
11. Version.
The full configuration version number. For example, 1.6.4.7. For details, see Version and revision numbering.
12. Update directory address.
The update URL.