[wechat applet] collaborative work and release

Author's brief introduction ： Su Liang （ Focus on web crawlers , Data analysis , On the way to learning the front end ）
Blog home page ： Su Liang .py The blog of
Series column ： Basic course of applet development
Aphorisms ： The sea is wide with fish , The sky is high and the birds are flying .
If you think the blogger's article is good , I hope you can support me for the third time in a row ！！！
Follow the likes collection

Working together

Permission management requirements

In large and medium-sized companies , The division of labor is very careful : The same applet project , There are usually different positions 、 Employees in different roles participate in design and development at the same time . At this time, for management needs , We urgently need different positions 、 The permissions of employees in different roles are divided into boundaries , Enable them to work together efficiently .（ for example ： Only set development permissions for developers （ Edit code …）, Only set test permissions for testers .）

Organizational structure of project members

• project manager - Coordinate the progress and risks of the whole project, and control the rhythm of the release of the applet

1. Product group - To demand
2. Design team - Work out the design scheme
3. Development Group - Code development
4. Test group - Project test

The development process of the applet

Member management of applet

Member management

It's divided into two parts ： Administrator's management of project members and administrator's management of experience personnel .
In the applet , The administrator has the maximum Authority , The member management of applet is mainly reflected in the administrator's management of applet project members and experience members , In addition to the administrator , The following is the division of project members and experience personnel ：

1. Members of the project

• Indicates participation in applet development 、 Members of the operation
• Can log in small program management background
• Administrators You can add 、 Delete project members , And set the roles of project members

2. Experience personnel

• Represents the members participating in the applet in-house test experience
• You can use the experience applet , But not a member of the project
• Administrators and project members Can be added 、 Delete experience members

Developer's permission description

The developer has the following permissions ：

1. Developer rights : You can use applet developer tools and code development for applet functions
2. Experience authority : You can use the experience applet
3. Login rights : Can log in small program management background , Administrator confirmation is not required
4. Development and setup : Set applet server domain name 、 Message push and scan ordinary link QR code to open applet
5. Tencent cloud management : Cloud development related settings

Add project members and experience members

Go to the applet page => Applet , You can see that we are our own administrators .

Drop down we can add and edit project members and experience members .

The version of the applet

Different versions in the software development process

In the process of software development , According to different time nodes , Different software versions will be produced , for example :

• While developers write code , Self test the project code ( Development version ) Until the program reaches a stable and experiential state , Developers send the experience version to product managers and testers for experience testing , Finally, the program is repaired Bug after , Release the official version for external users .

Applet version

The applet version is divided into 4 Different stages , Each stage will have different versions . Respectively ：

1. Development version
   Use developer tools , You can upload the code to the development version . The development version only keeps the latest uploaded code of each person . Click submit for review , The code can be submitted for review . The development version can be deleted , It does not affect the code of the online version and the version under review .

2. Experience version
   You can select a development version as the experience version , And choose an experience version .

3. Version under review
   There can only be one copy of the code under review . The audit results can be published online , You can also resubmit for approval directly , Overwrite the original approved version .

4. Online version
   The version of the code used by all users online , The version code is updated after the new version code is released .

The release of the applet goes online

Upload code

In our developer tools , Upload the Prepared applet code , Set the version number and project notes and click upload .

Check the uploaded version in the background

Select version management on the homepage of the applet ：

Here we can see that the newly uploaded version is in the development version

Submit audit

Why submit for review ： In order to ensure the quality of small programs , And comply with relevant specifications , The release of small programs needs to be reviewed by Tencent .

How to submit for review ： In the list of development versions , Click on “ Submit audit ” After the button , Fill in the relevant information according to the prompts on the page , You can submit the applet to Tencent official for review .

Published online

After approval , The administrator will receive the notification that the applet has passed the audit in the wechat , In the list of approved versions , Click on “ Release ” After the button , You can “ Approved by ” The version of is released as “ Online version ”, For all applet users to access and use .