Release and multi-version upgrade method and system

Abstract

The invention discloses an edition release multi-edition upgrading method. The edition release multi-edition upgrading method comprises the steps that when a server stores edition release, an upgrade catalog of a corresponding type is set for versions of each type; according to the upgrade catalog, upgrade sub-catalogs of the versions are set for the versions of the same type; version upgrade requests sent by clients are received, and information of the upgrade sub-catalog of the current version of the client is read; according to the upgrade sub-catalog of the current version, the other versions of the same type are obtained; the stored upgrade versions are matched with the information of the current version of the client respectively, and the upgrade version is obtained; the versions of the same type of the current type correspond to the new upgrade versions respectively; according to the number of the upgrade versions, the same number of clients are selected from all the clients requesting upgrading to be used as samples of the upgrade versions, and the upgradable allowance of each sample is judged; when the upgrade allowance of the sample is enough, the corresponding upgrade versions and the related upgrade information are returned to the request clients inside the samples.

Description

technical field [0001] The present application relates to the technical field of version upgrade management and control, and in particular, relates to a method and system for publishing multi-version upgrades. Background technique [0002] The existing electronic equipment system version needs to be updated according to the database system and new technology, so the product system needs to be updated according to the new version. And now there may be more than one type of upgrade version. Generally, for the client version, an upgradeable target version is provided in the background system, that is, a release version, which contains multiple upgradeable versions. In order to compare the functional effects of various product versions, it is often necessary to compare the effect of sample upgrades on the client product versions. During the sampling comparison process, it is necessary to set the client sample size of each upgraded version to be consistent in order to obtain accu...

AI Technical Summary

Problems solved by technology

[0011] 1. In the existing technology, the serial upgrade method is adopted for the client version, the target version is upgraded sequentially, and the upgrade of the next version is started on the basis of the upgrade of the previous version. In this way, the release upgrade time will be delayed. The linear increase, consumes a lot of time

[0012] 2. During the version upgrade process, because multiple upgrades need to be performed serially, the upgrade time period and time consumption of different release versions will be different, and due to different time periods and different client attributes, such as activity and regional attributes, this will lead to inconsistencies in the number of client samples in the upgrade time period of different releases, which will eventually lead to differences in product comparison effects

[0013] 3. The existing technology upgrades the version in a serial manner. When there is a requirement for the number of client samples, it is easy to exceed the total number of client samples, which may lead to insufficient samples for subsequent version upgrades, resulting in customer Inconsistencies in the number of end-to-end samples will eventually result in differences in the comparison of product version effects

[0014] 4. When the version serial upgrade needs to compare the effects of many versions, it is also necessary to compare each version to determine the target version and arrange the upgrade sequence of each version. The operation is cumbersome and takes a certain amount of time

Images