[SERVER-82768] Sort out how to unblock WiredTiger from releasing on v4.4 Created: 03/Nov/23  Updated: 06/Dec/23  Resolved: 06/Dec/23

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

Type: Bug Priority: Blocker - P1
Reporter: Steve Gross Assignee: Steve Gross
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Operating System: ALL
Participants:

 Description   

Currently, WiredTiger is unable to carry out its release procedure on v4.4.26 (upcoming release). This is due to a mismatch in WT's release procedure wrt the design of the enterprise repo consolidation epic (https://jira.mongodb.org/browse/DEVPROD-287?filter=45823).

See details in slack thread: https://mongodb.slack.com/archives/C0V896UV8/p1699023428981369?thread_ts=1698772491.082619&cid=C0V896UV8



 Comments   
Comment by Alex Neben [ 14/Nov/23 ]

Is this still a problem? Should this ticket be closed?

Comment by Luke Chen [ 05/Nov/23 ]

The rest of the steps went through successfully and WT commits are now in the mongodb/mongo repository. 

britt.snyman@mongodb.com maria.prinus@mongodb.com over to you for the 4.4.26-rc0 release trigger. 

juan.gu@mongodb.com steve.gross@mongodb.com thanks for organizing the revert to unblock the mongo 4.4 release. 

Comment by Juan Gu [ 03/Nov/23 ]

luke.chen@mongodb.com  you can start your rendering process now. Let me know if there is any problems. 

Comment by Steve Gross [ 03/Nov/23 ]

maria.prinus@mongodb.com Branch is unfrozen.

Comment by Maria Prinus [ 03/Nov/23 ]

juan.gu@mongodb.com I unfroze v4.4 branch, please, proceed with the changes.

Comment by Juan Gu [ 03/Nov/23 ]

I have done #3 and #4.
britt.snyman@mongodb.com  can you Unfreeze v4.4 release candidate branch

Comment by Juan Gu [ 03/Nov/23 ]

I have done the #2, 10gen/mongo v4.4 and mongodb/mongo v4.4 are having same git hash for all the commits now 

Comment by Steve Gross [ 03/Nov/23 ]

Per conversation, the plan is:

  1. Freeze v4.4 release candidate branch
  2. Force 10gen/mongo (v4.4 branch) to mirror latest commit of mongodb/mongo (v4.4 branch) as of ~today
  3. Make sure crbot is properly syncing commits FROM mongodb/mongo TO 10gen/mongo
  4. Adjust settings (GH, evergreen.yml, etc.) to reflect "old" way of managing repo
  5. Unfreeze v4.4 release candidate branch

The result of this should restore the way repo/evergreen was configured, which should unblock WiredTiger and !WiredTiger devs for v4.4 release.

Generated at Thu Feb 08 06:50:13 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.