A method, device, electronic device and storage medium for planning a release window

Abstract

The present application provides a release window planning method, device, electronic device and storage medium, which analyzes the project release requirements of the project to be released, determines the release time node experienced by updating the target application system involved in the project to be released to the system release version that meets the project release requirements; for each release time node, in response to the window configuration operation, creates a release window corresponding to the release time node; the release window is used to indicate the version information to be delivered at the release time node; based on the release time node corresponding to each release window, generates a release planning timeline for the project to be released. In this way, by creating a release window for the project to be released at each release time node, the release planning timeline of the development platform to which the project to be released belongs can be generated, so that the development team can clarify the update requirements of each project to be released at the release time node with the help of the release planning timeline, which can improve the accuracy of demand information synchronization.

Description

Technical Field

[0001] The present application relates to the field of data processing technology, and in particular to a release window planning method, device, electronic device and storage medium. Background Art

[0002] At present, the release mode of most application systems still exists in the form of release windows. The release window refers to the release time node (usually when the application system load is low) at which one or more teams can release the updated application system to the production environment.

[0003] During the release process of the target application system involved in the project to be released, the release time node, release resource allocation and other information of the target application system need to be transmitted manually between multiple application systems or teams. For some simple projects to be released, since the number of application systems or release requirements involved are small, the release time node, release resource allocation and other information are relatively simple, and the manual transmission of information is relatively simple and convenient; however, for projects to be released involving multiple application systems, or when the release process of the target application system involved in the project to be released requires the cooperation of multiple teams, simply relying on the manual transmission of information to transmit the release time node and other information of each target application system between multiple application systems or teams is prone to delays, omissions, and uneven release resource allocation, which will affect the overall release progress of the project to be released. Summary of the invention

[0004] In view of this, the purpose of the present application is to provide a release window planning method, device, electronic device and storage medium, which can generate a release planning timeline for the project to be released by creating a release window corresponding to each release time node of the project to be released, so that the project responsible team can use the various release windows in the release planning timeline to clarify the system update requirements of the target application system in the project to be released at the release time node, and no longer need to manually transmit project requirement information, which can improve the timeliness and accuracy of information synchronization.

[0005] The present application embodiment provides a method for planning a release window, the planning method comprising:

[0006] By analyzing the project release requirements of the project to be released, determining the release time node experienced by updating the target application system involved in the project to be released to the system release version that meets the project release requirements;

[0007] For each release time node, in response to the window configuration operation, a release window corresponding to the release time node is created; the release window is used to indicate the version information to be delivered at the release time node;

[0008] Based on the release time node corresponding to each release window, each release window is arranged in reverse chronological order to generate a release planning timeline for the development platform to which the to-be-released project belongs.

[0009] In a possible implementation manner, after creating the publishing window corresponding to the publishing time node, the planning method further includes:

[0010] In response to the update version association operation, the release window is associated with the to-be-released version of the target application system, so as to update the target application system to the to-be-released version at the release time node.

[0011] In a possible implementation, in response to the update version association operation, associating the release window with the to-be-released version of the target application system includes:

[0012] In response to the update version association operation, a version association interface is displayed in the graphical user interface; wherein the version association interface displays window configuration items and system association items;

[0013] In response to a first configuration operation applied to the window configuration item, determining a publishing window to be associated;

[0014] In response to the second configuration operation applied to the system-related item, determining a target application system involved in the system update requirement delivered by the release window to be associated;

[0015] By identifying the historical release versions of the target application system, determining the to-be-released version corresponding to the target application system after the update is completed;

[0016] The release window to be associated is associated with the version to be released.

[0017] In a possible implementation manner, the version association interface displays historical version association items, and the planning method further includes:

[0018] In response to the historical version association operation applied to the historical version association item, the release window is associated with the historical release version of the target application system, so as to update the target application system with reference to the historical release version at the release time node.

[0019] In a possible implementation, in response to the window configuration operation, creating a publishing window corresponding to the publishing time node includes:

[0020] In response to the window configuration operation, a window adding interface is displayed in the graphical user interface; wherein the window adding interface includes a time configuration item;

[0021] In response to the time configuration operation for the time configuration item, by configuring the release time node, a window management page of the release time node is displayed in a graphical user interface; wherein the window management page displays system configuration items, requirement configuration items, and module configuration items;

[0022] In response to the third configuration operation for the system configuration item, determining a target application system updated at the release time node;

[0023] In response to the fourth configuration operation for the required configuration item, determining a system update requirement to be delivered by the target application system at the release time node;

[0024] In response to the fifth configuration operation for the module configuration item, determining in the target application system that a target service module needs to be updated according to the system update requirement;

[0025] A publishing window corresponding to the publishing time node is created based on the target application system, the system update requirement and the target service module.

[0026] In a possible implementation manner, the publishing window includes an update requirement query control and an update detail query control; after generating a publishing planning timeline of the development platform to which the to-be-published project belongs, the planning method further includes:

[0027] In response to a first trigger operation applied to the update requirement query control, displaying requirement detail information of the system update requirement in a graphical user interface;

[0028] In response to a second trigger operation applied to the update detail query control, update detail information of the target application system involved in the system update requirement is displayed in a graphical user interface.

[0029] In a possible implementation, the step of displaying detailed information of the system update requirement in a graphical user interface in response to the first trigger operation applied to the update requirement query control includes:

[0030] In response to the first trigger operation applied to the update demand query control, a demand display page is displayed in the graphical user interface; wherein the demand display page includes a demand display area and a demand selection area; the demand display area displays demand details information of the planned demand;

[0031] In response to a content adjustment operation applied to the demand selection area, the display content in the demand display area is adjusted to demand detail information of unplanned demands.

[0032] The embodiment of the present application further provides a planning device for publishing a window, the planning device comprising:

[0033] A node determination module is used to determine the release time node experienced by updating the target application system involved in the project to be released to a system release version that meets the project release requirements by analyzing the project release requirements;

[0034] A window creation module, for each release time node, in response to a window configuration operation, creating a release window corresponding to the release time node; the release window is used to indicate the version information to be delivered at the release time node;

[0035] The timeline planning module is used to arrange each publishing window in reverse chronological order based on the publishing time node corresponding to each publishing window, and generate a publishing planning timeline for the project to be published.

[0036] In a possible implementation, after creating the publishing window corresponding to the publishing time node, the planning device further includes a first version association module, where the first version association module is used to:

[0037] In response to the update version association operation, the release window is associated with the to-be-released version of the target application system, so as to update the target application system to the to-be-released version at the release time node.

[0038] In a possible implementation, when the first version association module is used to associate the release window with the to-be-released version of the target application system in response to the update version association operation, the first version association module is used to:

[0039] In response to the update version association operation, a version association interface is displayed in the graphical user interface; wherein the version association interface displays window configuration items and system association items;

[0040] In response to a first configuration operation applied to the window configuration item, determining a publishing window to be associated;

[0041] In response to the second configuration operation applied to the system association item, determining a target application system involved in the system update requirement delivered by the release window to be associated;

[0042] By identifying the historical release versions of the target application system, determining the to-be-released version corresponding to the target application system after the update is completed;

[0043] The release window to be associated is associated with the version to be released.

[0044] In a possible implementation, the version association interface displays historical version association items, and the planning device further includes a second version association module, which is used to:

[0045] In response to the historical version association operation applied to the historical version association item, the release window is associated with the historical release version of the target application system, so as to update the target application system with reference to the historical release version at the release time node.

[0046] In a possible implementation, when the window creation module is used to create a publishing window corresponding to the publishing time node in response to a window configuration operation, the window creation module is used to:

[0047] In response to the window configuration operation, a window adding interface is displayed in the graphical user interface; wherein the window adding interface includes a time configuration item;

[0048] In response to the time configuration operation for the time configuration item, by configuring the release time node, a window management page of the release time node is displayed in a graphical user interface; wherein the window management page displays system configuration items, requirement configuration items, and module configuration items;

[0049] In response to the third configuration operation for the system configuration item, determining a target application system updated at the release time node;

[0050] In response to the fourth configuration operation for the required configuration item, determining a system update requirement to be delivered by the target application system at the release time node;

[0051] In response to the fifth configuration operation for the module configuration item, determining in the target application system that a target service module needs to be updated according to the system update requirement;

[0052] A publishing window corresponding to the publishing time node is created based on the target application system, the system update requirement and the target service module.

[0053] In a possible implementation, the release window includes an update requirement query control and an update detail query control; after generating a release planning timeline for the development platform to which the to-be-released project belongs, the planning device further includes a detail display module, the detail display module being used to:

[0054] In response to a first trigger operation applied to the update requirement query control, displaying requirement detail information of the system update requirement in a graphical user interface;

[0055] In response to a second trigger operation applied to the update detail query control, update detail information of the target application system involved in the system update requirement is displayed in a graphical user interface.

[0056] In a possible implementation, when the detail display module is used to respond to the first trigger operation applied to the update requirement query control and display the requirement detail information of the system update requirement in the graphical user interface, the detail display module is used to:

[0057] In response to the first trigger operation applied to the update demand query control, a demand display page is displayed in the graphical user interface; wherein the demand display page includes a demand display area and a demand selection area; the demand display area displays demand details information of the planned demand;

[0058] In response to a content adjustment operation applied to the demand selection area, the display content in the demand display area is adjusted to demand detail information of unplanned demands.

[0059] An embodiment of the present application also provides an electronic device, comprising: a processor, a memory and a bus, wherein the memory stores machine-readable instructions executable by the processor, and when the electronic device is running, the processor and the memory communicate through the bus, and when the machine-readable instructions are executed by the processor, the steps of the planning method for the release window as described above are performed.

[0060] An embodiment of the present application further provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the steps of the above-mentioned release window planning method are executed.

[0061] The release window planning method, device, electronic device and storage medium provided in the embodiments of the present application analyze the project release requirements of the project to be released, determine the release time node experienced by updating the target application system involved in the project to be released to the system release version that meets the project release requirements; for each release time node, in response to the window configuration operation, create a release window corresponding to the release time node; the release window is used to indicate the version information to be delivered at the release time node; based on the release time node corresponding to each release window, each release window is arranged in reverse chronological order to generate a release planning timeline for the development platform to which the project to be released belongs. In this way, a release planning timeline can be generated by creating a corresponding release window for each release time node of the project to be released, so that the development team can use the release planning timeline to clarify the version information of each project to be released at each release time node, so that the responsible team can reasonably allocate release resources, avoid delays and omissions in the transmission of information such as update requirements, and improve the timeliness and accuracy of demand information synchronization; and, the release window is associated with the version to be released of the target application system, so that developers can use the project development window to timely implement updates to the target application system at the corresponding release time node, thereby avoiding delays in the release time of each release version of the target application system.

[0062] In order to make the above-mentioned objects, features and advantages of the present application more obvious and easy to understand, preferred embodiments are specifically cited below and described in detail with reference to the attached drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0063] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required for use in the embodiments will be briefly introduced below. It should be understood that the following drawings only show certain embodiments of the present application and therefore should not be regarded as limiting the scope. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without paying creative work.

[0064] Figure 1 A flowchart of a method for planning a release window provided in an embodiment of the present application;

[0065] Figure 2 A schematic diagram of a window adding interface provided in an embodiment of the present application;

[0066] Figure 3 A schematic diagram of a release planning timeline for a project to be released provided in an embodiment of the present application;

[0067] Figure 4 A schematic diagram of a version association interface provided in an embodiment of the present application;

[0068] Figure 5 A schematic diagram of a publishing window provided in an embodiment of the present application;

[0069] Figure 6 A schematic diagram of a demand display page provided in an embodiment of the present application;

[0070] Figure 7 A schematic diagram of a version details page provided in an embodiment of the present application;

[0071] Figure 8 A schematic diagram of the structure of a planning device for publishing a window provided in an embodiment of the present application;

[0072] Fig. 9 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0073] To make the purpose, technical scheme and advantages of the embodiments of the present application clearer, the technical scheme in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all of the embodiments. The components of the embodiments of the present application usually described and shown in the drawings here can be arranged and designed in various different configurations. Therefore, the following detailed description of the embodiments of the present application provided in the drawings is not intended to limit the scope of the application claimed for protection, but merely represents the selected embodiments of the present application. Based on the embodiments of the present application, each other embodiment obtained by those skilled in the art without making creative work belongs to the scope of protection of the present application.

[0074] According to research, in the process of releasing the target application system involved in the project to be released, the release time node, release resource allocation and other information of the target application system need to be transmitted manually between multiple application systems or teams. For some simple projects to be released, since the number of application systems or release requirements involved are small, the release time node, release resource allocation and other information are relatively simple, and the manual transmission of information is relatively simple and convenient; however, for projects to be released involving multiple application systems, or when the release process of the target application system involved in the project to be released requires cooperation among multiple teams, simply relying on the manual transmission of information to transmit the release time node and other information of each target application system between multiple application systems or teams is prone to delays, omissions, and uneven release resource allocation, which will affect the overall release progress of the project to be released.

[0075] Based on this, an embodiment of the present application provides a release window planning method, which can generate a release planning timeline for the development platform to which the project to be released belongs by creating a release window corresponding to each release time node of the project to be released, so that the development team can use the release planning timeline to clarify the version information of each project to be released at each release time node, thereby enabling the responsible team to reasonably allocate release resources, avoid delays and omissions in the transmission of information such as update requirements, and improve the timeliness and accuracy of demand information synchronization.

[0076] See also Figure 1 , Figure 1 This is a flow chart of a method for planning a release window provided in an embodiment of the present application. Figure 1 As shown in , the release window planning method provided by the embodiment of the present application includes:

[0077] S101 , by analyzing the project release requirements of the project to be released, determining the release time node experienced by updating the target application system involved in the project to be released to the system release version that meets the project release requirements.

[0078] S102. For each release time node, in response to a window configuration operation, create a release window corresponding to the release time node; the release window is used to indicate version information to be delivered at the release time node.

[0079] S103: Based on the release time node corresponding to each release window, each release window is arranged in reverse chronological order to generate a release planning timeline for the development platform to which the to-be-released project belongs.

[0080] A release window planning method provided in an embodiment of the present application analyzes the project release requirements of the project to be released, determines the various release time nodes that need to be experienced in order to release the target application system involved in the project to be released to the system release version, thereby realizing the planning of the version release time of each intermediate version of the target application system; after planning the release time nodes that the target application system needs to experience, a release window for the release time node can be created for each release time node, so as to indicate the version information to be delivered at the release time node through the release window, and then, the development team can use the release window to clarify the version information to be delivered at the release time node; at the same time, in order to enable the responsible team to intuitively understand the overall release progress of the project to be released, each release window created can be combined in reverse chronological order to generate a release planning timeline for the development platform to which the project to be released belongs, so that the development team can understand the release requirements in the near future through the release planning timeline.

[0081] Here, for a project to be released, considering that its project release requirements may involve updating of multiple target application systems, therefore, if you want to complete the project release requirements of the project to be released, you need to update each target application system involved in the project release requirements one by one; and for each target application system, updating to a system release version that meets the project release requirements requires a complex function improvement process, and improving the relevant application functions (i.e., service modules) one by one; therefore, in order to provide an orderly function improvement environment in the process of updating the target application system, the target application needs to be divided into multiple release time nodes in the function improvement process, so that the responsible team can complete the improvement of the application function at the corresponding release time nodes, thereby ensuring the overall release progress of each project to be released.

[0082] In step S101, the project release requirements of the project to be released are analyzed to determine the target application system (and / or service modules in the target application system) to be updated as indicated by the project release requirements; for the determined target application system, combined with the actual implementation progress of the target application system, the release time node that needs to be experienced to update the target application system to the system release version that meets the project release requirements is determined.

[0083] Here, in order to visualize the delivery content (ie, the version information to be delivered) at each release time node, a release window of the release time node is created for each release time node to display the version information to be delivered at the release time node through the release window.

[0084] In step S102, for each release time node involved in the update process of the target application system, the project management planner in the project responsible team can complete the configuration of the release window corresponding to the release time node by applying the window configuration operation in the release window management page, so as to display the version information that the developer needs to deliver at the release time node through the release window.

[0085] Among them, the version information may include the target application system that needs to be updated, the system update requirements, and the target service modules, etc.; the system update requirements can indicate the number of system update requirements at the release time node, the number of target application systems involved in the system update requirements, the number of service modules that need to be updated in the target application system, and other information.

[0086] Specifically, the release window management page can be displayed in the graphical user interface, and in response to the window configuration operations performed by the project management planner in the release window management interface, the version information configuration is completed by filling in the system configuration items, requirement configuration items, module configuration items, etc., and the release window corresponding to the release time node is created.

[0087] In one implementation, in response to the window configuration operation, creating a publishing window corresponding to the publishing time node includes:

[0088] S1021. In response to the window configuration operation, a window adding interface is displayed in the graphical user interface.

[0089] In this step, when the project management planner has a project window configuration requirement, the display of a new window interface can be triggered by executing a window configuration operation, so as to complete the setting of the release time node in the new window interface; specifically, in response to the window configuration operation performed by the project management planner, a new window interface that can be used for the release time node configuration is displayed in the graphical user interface; the new window interface includes a time configuration item.

[0090] See also Figure 2 , Figure 2 This is a schematic diagram of a window adding interface provided in an embodiment of the present application. Figure 2 As shown, a new window interface 2b is displayed in the graphical user interface 2a, and a time configuration item 2c is displayed in the new window interface 2b. The project management planner can complete the configuration of the time configuration item 2c by selection or input to complete the setting of the release time node.

[0091] S1022: In response to the time configuration operation for the time configuration item, a window management page is displayed in a graphical user interface.

[0092] In this step, the project management planner can complete the configuration of the time configuration items in the new window interface. When the release time node is clear, it can trigger the entry into the window management page for configuring the target application system, system update requirements, target service modules and other contents included in the version information to be delivered at the release time node. By configuring the target application system, system update requirements, target service modules and other contents in the window management page, a release window corresponding to the release time node is created.

[0093] Among them, the window management page displays system configuration items, requirement configuration items and module configuration items.

[0094] S1023: In response to the third configuration operation on the system configuration item, determine the target application system updated at the release time node.

[0095] In this step, the project management planner can configure the system configuration items to specify the target application system that needs to be updated with functions at the release time node; specifically, in response to the third configuration operation applied by the project management planner to the system configuration items, the target application system that needs to be updated with functions at the release time node is determined.

[0096] S1024: In response to the fourth configuration operation for the required configuration item, determine the system update requirement that needs to be delivered by the target application system at the release time node.

[0097] In this step, after completing the configuration of the target application system, the project management planner can also configure the requirement configuration items to clarify the system update requirements that the target application system needs to meet at the release time node; specifically, in response to the fourth configuration operation applied by the project management planner to the requirement configuration items, determine the system update requirements that the target application system needs to meet at the release time node.

[0098] S1025. In response to the fifth configuration operation for the module configuration item, it is determined that in the target application system, a target service module needs to be updated according to the system update requirement.

[0099] In this step, the project management planner can further associate the target service module in the target application system that actually needs to be updated according to the system update requirements by configuring the module configuration items; specifically, in response to the fifth configuration operation applied by the project management planner to the module configuration items, it is determined that the target service module in the target application system needs to be updated according to the system update requirements.

[0100] S1026: Based on the target application system, the system update requirement and the target service module, create a publishing window corresponding to the publishing time node.

[0101] In this step, the system update requirements such as the number of target application systems that need to be updated and the number of target service modules that need to be updated in each target application system are counted, the number of target application systems, the number of target service modules, the version information of target application systems and target service modules are integrated, and a release window corresponding to the release time node is created.

[0102] Here, after completing the creation of the release windows corresponding to each release time node one by one, in order to facilitate project management planners or developers to monitor the overall release progress of the projects to be released, and to timely understand the system update requirements of the projects to be released in the near future, the release windows can be sorted in reverse chronological order.

[0103] In step S103, in combination with the release time node corresponding to each release window, each release window created is arranged in reverse chronological order to generate a release planning timeline for the development platform to which the project to be released belongs, so as to intuitively display the release progress and historical distribution information of each project to be released in the development platform through the release planning timeline; and, priority is given to displaying release windows that are closer to the current time, so that project management planners or developers can promptly understand the system update requirements that need to be met in the near future, and it is also helpful for project management planners or developers to grasp the current release progress of each project to be released.

[0104] See also Figure 3 , Figure 3 This is a schematic diagram of the release planning timeline of the project to be released provided in the embodiment of the present application. Figure 3 As shown, the release planning timeline 3a of the project to be released includes multiple release windows 3b, and each release window 3b is arranged in reverse chronological order; each release window 3b displays a release time node 3b-1 and version information 3b-2; wherein, the version information 3b-2 includes the number of system update requirements, the number of target application systems involved in the system update requirements, and the number of service modules that need to be updated in the target application systems.

[0105] In order to update the target application system to a more standardized over-release version at each release time node involved, the release window can be associated with the release version to update the target application system to the corresponding release version at the release time node corresponding to the release window.

[0106] In one implementation, after creating the publishing window corresponding to the publishing time node, the planning method further includes:

[0107] S104 . In response to the update version association operation, the release window is associated with the to-be-released version of the target application system, so as to update the target application system to the to-be-released version at the release time node.

[0108] In this step, the project management planner or developer can associate the release window with the to-be-released version of the target application system by updating the version association operation, so that the developer can update the target application system to the release time node of the to-be-released version with the help of the release window;

[0109] Specifically, in response to the update version association operation imposed by the project management planner or developer, the release window can be associated with the to-be-released version of the target application system by configuring the window configuration items and system association items in the version association interface, so that the developer can use the project development window to update the target application system to the to-be-released version at the release time node, thereby avoiding delays in the release time of various release versions of the target application system.

[0110] In one implementation, step S104 includes:

[0111] S1041. In response to the update version association operation, display a version association interface in the graphical user interface.

[0112] In this step, when the project management planner or developer needs to associate the release window with the release version of the target application system, the version association operation can be updated to trigger the display of the version association interface in the graphical user interface, so that the release version of the target application system can be associated with the release window by configuring the release window and the target application system that need to be associated in the version association interface.

[0113] The version association interface displays window configuration items and system association items.

[0114] S1042: In response to a first configuration operation applied to the window configuration item, determine a publishing window to be associated.

[0115] In this step, the project management planner can specify the release window that needs to be associated with the target application system by configuring the window configuration item; specifically, in response to the first configuration operation applied by the project management planner to the window configuration item, the release window to be associated with the target application system is determined.

[0116] S1043: In response to the second configuration operation applied to the system-related item, determine a target application system to which the release window to be associated indicates delivery.

[0117] In this step, the project management planner can configure the system association items to specify the target application system that needs to be associated with the release window to be associated; specifically, in response to the second configuration operation applied by the project management planner to the system association items, the target application system indicated for delivery by the release window to be associated is determined.

[0118] Here, the purpose of associating the release window with the target application system is to update the target application system to the to-be-released version associated with the release window at the release time node corresponding to the release window, thereby realizing the planning of the release time of the to-be-released version; therefore, after selecting the target application system, it is also necessary to clarify the to-be-released version planned to be released by the target application system at the release time node corresponding to the release window.

[0119] In order to ensure that the version to be released will not be repeated with the historical release version of the target application system, when determining the version to be released of the target application system, it is necessary to refer to the historical release version of the target application system that has been released.

[0120] S1044: Determine the to-be-released version corresponding to the target application system after the update is completed by identifying the historical released versions of the target application system.

[0121] In this step, the historical release versions of the target application system are identified to determine the historical version numbers of the historical release versions; based on the historical version numbers, the to-be-released version corresponding to the target application system is determined by automatically generating a new version number.

[0122] The update version number of the version to be released shall not be repeated with the historical version number of any historically released version.

[0123] Here, when the project management planner has a release version planning requirement, he or she can also adjust the version to be released corresponding to the target application system by adjusting the newly added version number; specifically, in response to the adjustment operation applied to the newly added version number, adjust the version to be released corresponding to the target application system.

[0124] S1045: Associating the release window to be associated with the version to be released.

[0125] Here, in order to reduce the difficulty of updating the target application system and enable developers to update the target application system based on historical release versions, the release window can also be associated with the historical release version of the target application system, so that when developers update the target application system at the development time node corresponding to the release window, they can refer to the historical release version of the target application system.

[0126] In one implementation, the version association interface displays historical version association items, and the planning method further includes:

[0127] S1046. In response to the historical version association operation applied to the historical version association item, the publishing window is associated with the historical published version of the target application system, so as to update the target application system with reference to the historical published version at the publishing time node.

[0128] In this step, the project management planner can use the historical version association operation to clearly specify the need to associate the release window with the historical release version of the target application system, so as to update the target application system with reference to the historical release version at the release time node corresponding to the release window; specifically, in response to the historical version association operation applied by the project management planner to the historical version association item displayed in the version association interface, the release window is associated with the historical release version of the target application system.

[0129] See also Figure 4 , Figure 4 This is a schematic diagram of a version association interface provided by an embodiment of the present application. Figure 4 As shown, the version association interface 4a displays a window configuration item 4b and a system association item 4c. The project management planner or developer can configure the release window to be associated with the help of the window configuration item 4b; the project management planner or developer can configure the target application system to be delivered to the release window with the help of the system association item 4c; the version association interface 4a also displays a version number column 4d, and the version number column 4d can display the updated version number of the version to be released corresponding to the target application system; the version association interface 4a also displays a historical version association item 4e, and the project management planner or developer can associate the release window with the historical release version of the target application system with the help of the historical version association item 4e.

[0130] Here, the project management planner or developer can also view the requirement details of the system update requirement and the update details of the target application system required to be updated by the system update requirement through the release window.

[0131] In one embodiment, the publishing window includes an update requirement query control and an update detail query control; after generating the publishing planning timeline of the to-be-published project, the planning method further includes:

[0132] S105 . In response to a first trigger operation applied to the update requirement query control, detailed information of the system update requirement is displayed in a graphical user interface.

[0133] In this step, it is considered that in the release window that constitutes the release planning timeline, only the release time node, the number of system update requirements, the number of target application systems, the number of service modules that need to be updated in the target application system and other system update requirements can be displayed in thumbnail form, making it impossible for project management planners or developers to understand the detailed information of the system update requirements in detail.

[0134] Therefore, in order to enable the project management planner or developer to fully understand the detailed information of the system update requirement, an update requirement query control is set in the release window. The project management planner or developer can trigger the display of the detailed information of the system update requirement in the graphical user interface by triggering the update requirement query control;

[0135] Specifically, in response to a first trigger operation applied by a project management planner or a developer to an update requirement query control, the display of requirement details of the system update requirement in the graphical user interface is triggered.

[0136] Here, considering that the version information at the release time node includes a large number of system update requirements, the time node viewed by the user may include delivered system update requirements and undelivered system update requirements. Therefore, in order to assist users in distinguishing the delivery status of system update requirements, the requirement details information of planned requirements and unplanned requirements can be displayed separately in the requirement display page.

[0137] In one embodiment, the step of displaying the requirement details of the system update requirement in a graphical user interface in response to the first trigger operation applied to the update requirement query control includes:

[0138] S1051. In response to a first trigger operation applied to the update requirement query control, a requirement display page is displayed in a graphical user interface.

[0139] In this step, the project management planner or developer can trigger the update requirement query control to enter the requirement display page, so as to view the requirement details information of each system update requirement on the requirement display page; specifically, in response to the first trigger operation applied by the project management planner or developer to the update requirement query control, the requirement display page is triggered to be displayed in the graphical user interface; and the requirement details information of each planned requirement that has been executed among the multiple system update requirements is displayed in the requirement display area of ​​the requirement display page.

[0140] In addition to the demand display area, the demand display page also includes a demand selection area. Project management planners or developers can use the demand selection area to switch the demand detail information displayed in the demand display area; that is, the demand detail information of planned demands displayed in the display area can be switched to the demand detail information of unplanned demands.

[0141] The demand display page includes a demand display area and a demand selection area; the demand display area displays demand details information of planned demands.

[0142] S1052: In response to the content adjustment operation applied to the demand selection area, the display content in the demand display area is adjusted to demand detail information of unplanned demands.

[0143] In this step, the project management planner or developer can trigger the switching of the displayed content in the requirement display area by applying a content adjustment operation in the requirement selection area; specifically, in response to the content adjustment operation applied by the project management planner or developer to the requirement selection area, the displayed content in the requirement display area is adjusted to the requirement detail information of the unplanned requirements.

[0144] Here, the requirement selection area may include a planned requirement viewing control and an unplanned requirement viewing control. The project management planner or developer may select the requirement detail information to be viewed by triggering the planned requirement viewing control and the unplanned requirement viewing control.

[0145] S106 . In response to a second trigger operation applied to the update detail query control, update detail information of the target application system involved in the system update requirement is displayed in a graphical user interface.

[0146] In this step, an update detail query control is set in the publishing window, and the project management planner or developer can trigger the update detail query control to trigger the display of the update detail information of the target application system involved in the system update requirement, or the update detail information of the target service module to be updated in the target application system in the graphical user interface;

[0147] Specifically, in response to the second trigger operation applied by the project management planner or developer to the update details query control, the version details page is triggered to be displayed in the graphical user interface; and the update details information of the target application system involved in the system update requirement, or the update details information of the target service module that needs to be updated in the target application system is displayed in the version details page.

[0148] The update details information includes the system name of the target application system, the module name of each service module in the target application system, the version information of each service module, and the operations executable for the target application system and / or each service module.

[0149] See also Figure 5 , Figure 5 A schematic diagram of a publishing window provided in an embodiment of the present application. Figure 5 As shown, in addition to displaying the release time node 5b and version information 5c such as the number of system update requirements, the number of target application systems involved in the system update requirements, and the number of service modules that need to be updated in the target application systems, the release window 5a is also provided with an update requirement query control 5d and an update detail query control 5e; project management planners or developers can view the requirement detail information of the system update requirements through the update requirement query control 5d, and can view the update detail information of the target application systems involved in the system update requirements, or the update detail information of the target service modules that need to be updated in the target application systems, through the update detail query control 5e.

[0150] See also Figure 6 , Figure 6 A schematic diagram of a demand display page provided in an embodiment of the present application. Figure 6 As shown, the requirement display page 6a displays a requirement display area 6b and a requirement selection area 6c. The requirement selection area 6c displays a planned requirement viewing control 6c-1 and an unplanned requirement viewing control 6c-2. When the project management planner or developer does not select the display content, the requirement display area 6b displays the requirement details of the planned requirements by default; the project management planner or developer can view the requirement details of the unplanned requirements through the unplanned requirement viewing control 6c-2.

[0151] See also Figure 7 , Figure 7 This is a schematic diagram of a version details page provided in an embodiment of the present application. Figure 7 As shown, the version details page 7a displays the system name of the target application system 7b, the module name of each service module 7c in the target application system 7b, the version information of each service module 7c, and the operations that can be performed on the target application system 7b and / or each service module 7c.

[0152] The release window planning method provided in the embodiment of the present application analyzes the project release requirements of the project to be released, determines the release time nodes experienced by updating the target application system involved in the project to be released to the system release version that meets the project release requirements; for each release time node, creates a release window corresponding to the release time node in response to the window configuration operation; the release window is used to indicate the version information to be delivered at the release time node; based on the release time node corresponding to each release window, arranges each release window in reverse chronological order to generate a release planning timeline for the development platform to which the project to be released belongs. In this way, by creating a release window corresponding to each release time node of the project to be released, a release planning timeline of the development platform to which the project to be released belongs can be generated, so that the development team can use the release planning timeline to clarify the version information of each project to be released at each release time node, thereby enabling the responsible team to reasonably allocate release resources, avoid delays and omissions in the transmission of information such as update requirements, and improve the timeliness and accuracy of demand information synchronization; and, by associating the release window with the version to be released of the target application system, the developers can use the project development window to timely implement the update of the target application system at the corresponding release time node, thereby avoiding delays in the release time of each release version of the target application system.

[0153] See also Figure 8 , Figure 8 This is a schematic diagram of the structure of a planning device for publishing windows provided in an embodiment of the present application. Figure 8 As shown in , the planning device 800 includes:

[0154] The node determination module 810 is used to determine the release time node experienced by updating the target application system involved in the project to be released to the system release version that meets the project release requirement by analyzing the project release requirement;

[0155] The window creation module 820 is used to create a release window corresponding to each release time node in response to the window configuration operation; the release window is used to indicate the version information to be delivered at the release time node;

[0156] The timeline planning module 830 is used to arrange each publishing window in reverse chronological order based on the publishing time node corresponding to each publishing window, and generate a publishing planning timeline for the development platform to which the to-be-published project belongs.

[0157] Furthermore, after creating the publishing window corresponding to the publishing time node, the planning device 800 further includes a first version association module (not shown in the figure), and the first version association module is used to:

[0158] In response to the update version association operation, the release window is associated with the to-be-released version of the target application system, so as to update the target application system to the to-be-released version at the release time node.

[0159] Further, when the first version association module is used to associate the release window with the to-be-released version of the target application system in response to the update version association operation, the first version association module is used to:

[0160] In response to the update version association operation, a version association interface is displayed in the graphical user interface; wherein the version association interface displays window configuration items and system association items;

[0161] In response to a first configuration operation applied to the window configuration item, determining a publishing window to be associated;

[0162] In response to the second configuration operation applied to the system association item, determining a target application system to which the release window to be associated indicates delivery;

[0163] By identifying the historical release versions of the target application system, determining the to-be-released version corresponding to the target application system after the update is completed;

[0164] The release window to be associated is associated with the version to be released.

[0165] Furthermore, the version association interface displays historical version association items, and the planning device 800 further includes a second version association module (not shown in the figure), which is used to:

[0166] In response to the historical version association operation applied to the historical version association item, the release window is associated with the historical release version of the target application system, so as to update the target application system with reference to the historical release version at the release time node.

[0167] Furthermore, when the window creation module 820 is used to create a publishing window corresponding to the publishing time node in response to the window configuration operation, the window creation module 820 is used to:

[0168] In response to the window configuration operation, a window adding interface is displayed in the graphical user interface; wherein the window adding interface includes a time configuration item;

[0169] In response to the time configuration operation for the time configuration item, by configuring the release time node, a window management page of the release time node is displayed in a graphical user interface; wherein the window management page displays system configuration items, requirement configuration items, and module configuration items;

[0170] In response to the third configuration operation for the system configuration item, determining a target application system updated at the release time node;

[0171] In response to the fourth configuration operation for the required configuration item, determining a system update requirement to be delivered by the target application system at the release time node;

[0172] In response to the fifth configuration operation for the module configuration item, determining in the target application system that a target service module needs to be updated according to the system update requirement;

[0173] A publishing window corresponding to the publishing time node is created based on the target application system, the system update requirement and the target service module.

[0174] Furthermore, the release window includes an update requirement query control and an update detail query control; after generating the release planning timeline of the development platform to which the to-be-released project belongs, the planning device 500 further includes a detail display module (not shown in the figure), which is used to:

[0175] In response to a first trigger operation applied to the update requirement query control, displaying requirement detail information of the system update requirement in a graphical user interface;

[0176] In response to a second trigger operation applied to the update detail query control, update detail information of the target application system involved in the system update requirement is displayed in a graphical user interface.

[0177] In a possible implementation, when the detail display module is used to respond to the first trigger operation applied to the update requirement query control and display the requirement detail information of the system update requirement in the graphical user interface, the detail display module is used to:

[0178] In response to the first trigger operation applied to the update demand query control, a demand display page is displayed in the graphical user interface; wherein the demand display page includes a demand display area and a demand selection area; the demand display area displays demand details information of the planned demand;

[0179] In response to a content adjustment operation applied to the demand selection area, the display content in the demand display area is adjusted to demand detail information of unplanned demands.

[0180] The release window planning device provided in the embodiment of the present application analyzes the project release requirements of the project to be released, determines the release time node experienced by updating the target application system involved in the project to be released to the system release version that meets the project release requirements; for each release time node, in response to the window configuration operation, creates a release window corresponding to the release time node; the release window is used to indicate the version information to be delivered at the release time node; based on the release time node corresponding to each release window, each release window is arranged in reverse chronological order to generate a release planning timeline for the development platform to which the project to be released belongs. In this way, by creating a release window corresponding to each release time node of the project to be released, a release planning timeline of the development platform to which the project to be released belongs can be generated, so that the development team can use the release planning timeline to clarify the version information of each project to be released at each release time node, thereby enabling the responsible team to reasonably allocate release resources, avoid delays and omissions in the transmission of information such as update requirements, and improve the timeliness and accuracy of demand information synchronization; and, by associating the release window with the version to be released of the target application system, the developers can use the project development window to timely implement the update of the target application system at the corresponding release time node, thereby avoiding delays in the release time of each release version of the target application system.

[0181] See also Fig. 9 , Fig. 9 This is a schematic diagram of the structure of an electronic device provided in an embodiment of the present application. Fig. 9 As shown in , the electronic device 900 includes a processor 910 , a memory 920 and a bus 930 .

[0182] The memory 920 stores machine-readable instructions executable by the processor 910. When the electronic device 900 is running, the processor 910 communicates with the memory 920 via the bus 930. When the machine-readable instructions are executed by the processor 910, the above-mentioned Figure 1 The specific implementation of the steps of the method for planning the release window in the method embodiment shown can be found in the method embodiment, which will not be repeated here.

[0183] The present application also provides a computer-readable storage medium on which a computer program is stored. When the computer program is executed by a processor, the computer program can execute the above-mentioned Figure 1 The specific implementation of the steps of the method for planning the release window in the method embodiment shown can be found in the method embodiment, which will not be repeated here.

[0184] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0185] In the several embodiments provided in the present application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. The device embodiments described above are merely schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some communication interfaces, and the indirect coupling or communication connection of devices or units can be electrical, mechanical or other forms.

[0186] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0187] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0188] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a non-volatile computer-readable storage medium that is executable by a processor. Based on this understanding, the technical solution of the present application can essentially be embodied in the form of a software product, or in other words, the part that contributes to the prior art or the part of the technical solution. The computer software product is stored in a storage medium, including several instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0189] Finally, it should be noted that the above-described embodiments are only specific implementation methods of the present application, which are used to illustrate the technical solutions of the present application, rather than to limit them. The protection scope of the present application is not limited thereto. Although the present application is described in detail with reference to the above-mentioned embodiments, ordinary technicians in the field should understand that any technician familiar with the technical field can still modify the technical solutions recorded in the above-mentioned embodiments within the technical scope disclosed in the present application, or can easily think of changes, or make equivalent replacements for some of the technical features therein; and these modifications, changes or replacements do not make the essence of the corresponding technical solutions deviate from the spirit and scope of the technical solutions of the embodiments of the present application, and should be included in the protection scope of the present application. Therefore, the protection scope of the present application shall be based on the protection scope of the claims.

Claims

1. A method for planning a release window, characterized in that: The planning method includes: By analyzing the project release requirements of the project to be released, determining the release time node experienced by updating the target application system involved in the project to be released to the system release version that meets the project release requirements; For each release time node, in response to the window configuration operation, a release window corresponding to the release time node is created; the release window is used to indicate the version information to be delivered at the release time node; Based on the release time nodes corresponding to each release window, each release window is arranged in reverse chronological order to generate a release planning timeline for the development platform to which the to-be-released project belongs; After creating the publishing window corresponding to the publishing time node, the planning method further includes: In response to the update version association operation, the release window is associated with the to-be-released version of the target application system, so as to update the target application system to the to-be-released version at the release time node; The step of associating the release window with the to-be-released version of the target application system in response to the update version association operation includes: In response to the update version association operation, a version association interface is displayed in the graphical user interface; wherein the version association interface displays window configuration items and system association items; In response to a first configuration operation applied to the window configuration item, determining a publishing window to be associated; In response to the second configuration operation applied to the system association item, determining a target application system to which the release window to be associated indicates delivery; By identifying the historical release versions of the target application system, determining the to-be-released version corresponding to the target application system after the update is completed; The release window to be associated is associated with the version to be released.

2. The planning method according to claim 1, characterized in that: The version association interface displays historical version association items, and the planning method further includes: In response to the historical version association operation applied to the historical version association item, the release window is associated with the historical release version of the target application system, so as to update the target application system with reference to the historical release version at the release time node.

3. The planning method according to claim 1, characterized in that: The step of creating a publishing window corresponding to the publishing time node in response to the window configuration operation includes: In response to the window configuration operation, a window adding interface is displayed in the graphical user interface; wherein the window adding interface includes a time configuration item; In response to the time configuration operation for the time configuration item, by configuring the release time node, a window management page of the release time node is displayed in a graphical user interface; wherein the window management page displays system configuration items, requirement configuration items, and module configuration items; In response to the third configuration operation for the system configuration item, determining a target application system updated at the release time node; In response to the fourth configuration operation for the required configuration item, determining a system update requirement to be delivered by the target application system at the release time node; In response to the fifth configuration operation for the module configuration item, determining in the target application system that a target service module needs to be updated according to the system update requirement; A publishing window corresponding to the publishing time node is created based on the target application system, the system update requirement and the target service module.

4. The planning method according to claim 3, characterized in that: The publishing window includes an update requirement query control and an update detail query control; After generating the release planning timeline of the development platform to which the to-be-released project belongs, the planning method further includes: In response to a first trigger operation applied to the update requirement query control, displaying requirement detail information of the system update requirement in a graphical user interface; In response to a second trigger operation applied to the update detail query control, update detail information of the target application system involved in the system update requirement is displayed in a graphical user interface.

5. The planning method according to claim 4, characterized in that: The step of displaying detailed information of the system update requirement in a graphical user interface in response to the first trigger operation applied to the update requirement query control includes: In response to the first trigger operation applied to the update demand query control, a demand display page is displayed in the graphical user interface; wherein the demand display page includes a demand display area and a demand selection area; the demand display area displays demand details information of the planned demand; In response to a content adjustment operation applied to the demand selection area, the display content in the demand display area is adjusted to demand detail information of unplanned demands.

6. A planning device for a release window, characterized in that: The planning device comprises: A node determination module is used to determine the release time node experienced by updating the target application system involved in the project to be released to a system release version that meets the project release requirements by analyzing the project release requirements; A window creation module, for each release time node, in response to a window configuration operation, creating a release window corresponding to the release time node; the release window is used to indicate the version information to be delivered at the release time node; A timeline planning module is used to arrange each release window in reverse chronological order based on the release time node corresponding to each release window, and generate a release planning timeline for the development platform to which the to-be-released project belongs; After creating the publishing window corresponding to the publishing time node, the planning device further includes a first version association module, and the first version association module is used to: In response to the update version association operation, the release window is associated with the to-be-released version of the target application system, so as to update the target application system to the to-be-released version at the release time node; When the first version association module is used to associate the release window with the to-be-released version of the target application system in response to the update version association operation, the first version association module is used to: In response to the update version association operation, a version association interface is displayed in the graphical user interface; wherein the version association interface displays window configuration items and system association items; In response to a first configuration operation applied to the window configuration item, determining a publishing window to be associated; In response to the second configuration operation applied to the system association item, determining a target application system to which the release window to be associated indicates delivery; By identifying the historical release versions of the target application system, determining the to-be-released version corresponding to the target application system after the update is completed; The release window to be associated is associated with the version to be released.

7. An electronic device, characterized in that: include: A processor, a memory and a bus, wherein the memory stores machine-readable instructions executable by the processor, and when the electronic device is running, the processor and the memory communicate via the bus, and the machine-readable instructions are executed by the processor to execute the steps of the release window planning method as described in any one of claims 1 to 5.

8. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps of the method for planning a release window as claimed in any one of claims 1 to 5 are executed.

Images