[SERVER-61668] STM Branching Task Created: 20/Nov/21  Updated: 29/Oct/23  Resolved: 07/Dec/21

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 5.2.0

Type: Task Priority: Major - P3
Reporter: Vivian Ge (Inactive) Assignee: Robert Guo (Inactive)
Resolution: Fixed Votes: 0
Labels: branch-5.2, during-branch
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Gantt Start to Start
Related
related to SERVER-54430 STM Branching Task Closed
Backwards Compatibility: Fully Compatible
Sprint: STM 2021-12-13
Participants:
Story Points: 1

 Description   

The overview of the workflow: https://tinyurl.com/vr3tjba3

  • * Branch system_perf.yml for 5.2
    • Change most references from "master" to "v5.2" Remove the wt-develop variants from the v5.2 commit
  • Branch evergreen.yml for 5.2
    • After branching, in the 5.2 branch:
      • Change most references from "master" to "v5.2"
      • Remove the wt-develop variants from the v5.2 commit See work done in SERVER-35158.
  • Remove wt develop from system-perf.yml and evergreen.yml
    • Similar to what we've done for previous releases, the wt-develop build variants should be removed from the release MongoDB branches.

All of these main bullet points should be a separate commit but they should be pushed together in the same commit queue task. The reason they should be pushed as separate commits is in the case of needing to revert one aspect of this entire task.
 



 Comments   
Comment by Githook User [ 07/Dec/21 ]

Author:

{'name': 'Robert Guo', 'email': 'robert.guo@10gen.com', 'username': 'guoyr'}

Message: SERVER-61668 update constants for the 5.2 branch
Branch: v5.2
https://github.com/mongodb/mongo/commit/c29253cfe43366d3e04535a221e2ebef21267048

Comment by Brooke Miller [ 24/Nov/21 ]

Confirmed. Thanks siran.wang!

Comment by Siran Wang (Inactive) [ 24/Nov/21 ]

Sure, I update the link, should be working now.

Comment by Brooke Miller [ 23/Nov/21 ]

I actually don't have permissions to access that doc. Can you move it to the Dev Productivity shared drive in the 'STM' team folder location so that others on the team can view it?

Comment by Brooke Miller [ 23/Nov/21 ]

Thanks siran.wang!

Comment by Siran Wang (Inactive) [ 23/Nov/21 ]

Sure, just add it to the description.

Comment by Brooke Miller [ 23/Nov/21 ]

vivian.ge when you create these tickets, could you please indicate when we aim to perform the branching, to help us with scheduling? When do we aim to branch 5.2?

Comment by Brooke Miller [ 23/Nov/21 ]

siran.wang could you link us to the doc that you created that outlined the overview of how to perform these tasks?

Generated at Thu Feb 08 05:53:01 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.