# US 2021/0342139 A1 · Reliable feature graduation

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2021/0342139 A1
- Document ID: US20210342139A1
- Status: Published application
- Kind: A1
- Application number: 16/903,061
- Filed: 2020-06-16
- Published: 2021-11-04
- Earliest claimed: 2020-05-01
- Assignees: Microsoft Technlogy Licensing, LLC
- Applicants: Microsoft Technology Licensing, LLC
- Inventors: Nidhi VERMA; Ankur JAUHARI; Min SHAO; Shobana KRISHNAMOORTHY
- Web page: https://patentgrep.com/patent/US20210342139A1

## CPC

- G06F 8/65: Updates (security arrangements therefor G06F21/57)
- G06F 8/60: Software deployment
- G06F 8/658: Incremental updates; Differential updates
- G06F 11/3668: Testing of software
- G06F 8/77: Software metrics
- G06F 9/44521: {Dynamic linking or loading; Link editing at or after load time, e.g. Java class loading}
- G06F 9/44526: {Plug-ins; Add-ons}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Reliable feature deployment is provided. Features are evaluated for their readiness to be graduated and features that are ready to be graduated are added to a graduation list. When features are added to the graduation list, evaluation of the features is discontinued, thereby reducing the performance and runtime costs associated with deploying features. Furthermore, engineers can consult the graduation list to identify features that are ready for graduation, thereby reducing the risk of premature flight graduation. Data associated with features is analyzed to map the features to corresponding flights. In this way, when an engineer identifies a feature for graduation, the engineer is able to identify the corresponding flight (or flights) from the mapping. Even when a feature is selected for graduation, the present systems provide additional safeguards to ensure that corresponding flights are not improperly or prematurely graduated, thereby preventing a subpar customer experience.

## Claims

### Claim 1

A computer-implemented method for reliable feature graduation, the method comprising:
deploying code for a feature of a plurality of features to a plurality of tenants, wherein the deployed code is not enabled for execution;
initiating at least one control mechanism to enable the deployed code for use by a first subset of users associated with the plurality of tenants, wherein the at least one control mechanism is associated with at least one code stub that is not logically linked to the feature in the deployed code;
evaluating first data associated with use of the feature by the first subset of users;
initiating the at least one control mechanism to enable the deployed code for use by at least a second subset of users associated with the plurality of tenants;
evaluating second data associated with use of the feature by at least the second subset of users;
based on the evaluation of the first data and the second data, mapping the feature to the at least one code stub;
in response to the evaluation of the use of the feature, determining that the feature is ready to be graduated;
discontinuing evaluation of the feature; and
based on the mapping, removing the at least one code stub.

### Claim 2 (depends on 1)

The computer-implemented method of claim 1, the method further comprising:
receiving an indication to graduate the feature;
verifying that the feature has not been edited within a period of time; and
removing the at least one code stub associated with the feature.

### Claim 3 (depends on 2)

The computer-implemented method of claim 2, wherein the at least one code stub is removed based on a ramp down policy.

### Claim 4 (depends on 3)

The computer-implemented method of claim 3, wherein the ramp down policy specifies that the at least one code stub associated with the code deployed to the first subset of users be removed before the at least one code stub associated with the code deployed to the second subset of users.

### Claim 5 (depends on 1)

The computer-implemented method of claim 1, wherein evaluating use of the feature comprises evaluating runtime use of one or more resources associated with a cloud computing environment hosting the plurality of tenants.

### Claim 6 (depends on 1)

The computer-implemented method of claim 1, wherein evaluating use of the feature comprises collecting telemetry data regarding use of the feature by the first subset of users and the second subset of users.

### Claim 7 (depends on 1)

The computer-implemented method of claim 1, wherein determining that the feature is ready to be graduated further comprises determining that the feature has been enabled for all tenants of the plurality of tenants.

### Claim 8 (depends on 7)

The computer-implemented method of claim 7, wherein the first subset of users and the second subset of users are associated with all tenants of the plurality of tenants.

### Claim 9 (depends on 7)

The computer-implemented method of claim 7, wherein determining that the feature is ready to be graduated further comprises determining that the feature has not been edited for a period of time.

### Claim 10 (depends on 9)

The computer-implemented method of claim 9, wherein the period of time is within a range of 1 day to 60 days.

### Claim 11 (depends on 1)

The computer-implemented method of claim 1, the method further comprising:
based on the evaluation of the first data and the second data, linking the at least one code stub to the feature.

### Claim 12 (depends on 11)

The computer-implemented method of claim 11, wherein the at least one code stub is linked to the feature in a mapping table.

### Claim 13 (depends on 1)

The computer-implemented method of claim 1, the method further comprising:
receiving an indication to graduate the feature;
waiting a period of time; and
removing the at least one code stub associated with the feature.

### Claim 14

A system, comprising:
at least one processor; and
at least one memory storing computer-executable instructions that when executed by the at least one processor cause the system to:
deploy code for a feature of a plurality of features to a plurality of tenants, wherein the deployed code is not enabled for execution;
initiate at least one control mechanism to enable the deployed code for the plurality of tenants, wherein the at least one control mechanism is associated with at least one code stub that is not co-located with the feature in the deployed code;
evaluate data associated with use of the feature by the plurality of tenants;
based on the evaluation of the data associated with use of the feature, link the at least one code stub to the feature;
based on the evaluation of the use of the feature, determine that the feature is ready to be graduated;
discontinue evaluation of the feature; and
based on the mapping, remove the at least one code stub.

### Claim 15 (depends on 14)

The system of claim 14, the computer-executable instructions when executed further causing the system to:
receive an indication to graduate the feature;
verify that the feature has not been edited within a period of time; and
remove the at least one code stub associated with the feature.

### Claim 16 (depends on 15)

The system of claim 15, wherein the at least one code stub is removed based on a ramp down policy.

### Claim 17 (depends on 14)

The system of claim 14, wherein evaluating use of the feature comprises evaluating runtime use of one or more resources associated with a cloud computing environment hosting the plurality of tenants.

### Claim 18 (depends on 14)

The system of claim 14, wherein evaluating use of the feature comprises collecting telemetry data regarding use of the feature by the plurality of tenants.

### Claim 19

A computer storage medium storing computer-executable instructions that when executed a processor cause a computer system to:
deploy code for a feature of a plurality of features to a plurality of tenants, wherein the deployed code is not enabled for execution;
initiate at least one control mechanism to enable the deployed code for the plurality of tenants, wherein the at least one control mechanism is associated with at least one code stub that is not logically linked to the feature in the deployed code;
evaluate data associated with use of the feature by the plurality of tenants;
based on the evaluation of the data associated with use of the feature, link the at least one code stub to the feature;
based on the evaluation of the use of the feature, determine that the feature is ready to be graduated;
discontinue evaluation of the feature; and
based on the mapping, remove the at least one code stub.

### Claim 20 (depends on 19)

The computer storage medium of claim 19, the computer-executable instructions when executed further causing the computer system to:
receive an indication to graduate the feature;
verify that the feature has not been edited within a period of time; and
remove the at least one code stub associated with the feature.
