Shulou(Shulou.com)05/31 Report--

Most people do not understand the knowledge points of this article "what are the Milestone Maintainers information of Kubernetes?", so the editor summarizes the following content, detailed content, clear steps, and has a certain reference value. I hope you can get something after reading this article. Let's take a look at this "what are the Milestone Maintainers information of Kubernetes" article.

Milestone Maintainers belongs to Release Team and is responsible for maintaining the version of Milestone. Its members not only come from Release Team, but also include representatives of various SIG. This section focuses on milestone maintainer-related information from each SIG.

Generally speaking, people who can become Milestone Maintainers are people who are deeply involved in community contribution. Because, as a Milestone Maintainers, you need to identify which release a given feature or bug should be integrated into. In addition, you also need to know some release rules, such as you need to know the exact time point of each version of code freeze and other key information.

Milestone Maintainers authority

Milestone Maintainer needs to participate in a community meeting, design, and various discussions so that you can identify which issue and PR need to be addressed in a particular release.

As a Milestone Maintainer, you have the right to set milestone for issue or PR.

Apply to become a Milestone Maintainers

The process of applying to become a Milestone Maintainer is very simple and requires only three steps:

Submit PR to add yourself to the appropriate configuration file

Approved by Chairman SIG

Approved by Chairman Release Team

Submit PR

All the milestone maintainers. Milestone maintainers are recorded in the config/kubernetes/sig-release/teams.yaml file of https://github.com/kubernetes/org warehouse. To apply to become a Milestone Maintainer, you only need to submit a PR to add your own GitHub ID.

If you are a Release Team member, add yourself to milestone-maintainers 's maintainers list

If you are a representative selected by a SIG, add yourself to milestone-maintainers 's members list:

Note that when submitting the PR, the GitHub ID is sorted in ascending alphabetical order.

Approved by Chairman SIG

Usually there will be two or three chairmen for each SIG. You usually need to agree with a chairman beforehand, and at least one chairman needs the consent of at least one chairman before your PR can continue.

Release Team approval

Generally speaking, after SIG agrees to join a member, Release Team will not refuse, but if a SIG joins a lot of milestone maintainer, Release Team may raise an objection. In this case, it is recommended to add some background information to explain why it is necessary to join.

Add Milestone for PR and Issue

Take PR as an example. Once you recognize that you want a release to merge, you can reply / milestone v1.xx to inform the robot to set milestone for the PR, indicating that the PR needs to be merged in the v1.xx version:

After the robot is set up, the milestone information will be displayed on the right side of the PR, as shown in the following figure:

The above is about the content of this article on "what is the Milestone Maintainers information of Kubernetes?" I believe we all have a certain understanding. I hope the content shared by the editor will be helpful to you. If you want to know more about the relevant knowledge, please follow the industry information channel.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.