[SERVER-50849] Update FCV constants in server code base following 4.8 branch Created: 09/Sep/20  Updated: 29/Oct/23  Resolved: 08/Oct/20

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

Type: Task Priority: Major - P3
Reporter: Steven Vannelli Assignee: A. Jesse Jiryu Davis
Resolution: Fixed Votes: 0
Labels: branch-4.8, post-branch
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Cloners
clones SERVER-49802 Update FCV constants in server code b... Closed
Depends
depends on SERVER-51313 Update multiversion download script t... Closed
Duplicate
is duplicated by SERVER-49803 Update FCV constants in server code b... Closed
Gantt Dependency
Gantt End to End
Related
related to SERVER-49801 Update WireVersion after 4.7.0 release Closed
is related to SERVER-54434 Update FCV constants in server code b... Closed
Backwards Compatibility: Fully Compatible
Sprint: Repl 2020-10-19
Participants:
Linked BF Score: 0

 Description   

After branching for 4.8, the master branch must be updated to use the include the new 4.9 FCV constants. We must also update the references to last-lts, last-continuous, and latest to point to the updated versions.



 Comments   
Comment by Githook User [ 08/Oct/20 ]

Author:

{'name': 'A. Jesse Jiryu Davis', 'email': 'jesse@mongodb.com', 'username': 'ajdavis'}

Message: SERVER-50849 Update FCV constants to recognize 4.9 as latest
Branch: master
https://github.com/mongodb/mongo/commit/07c9a6208188039fcec9bd8edda461e521e72ad9

Comment by A. Jesse Jiryu Davis [ 07/Oct/20 ]

Jon Streets shared a video of how he, Jason, and Kelsey did it last time; I've added notes to the "Guide to updating FCV constants in the server" doc. I have a meeting with Jon tomorrow at 1:30pm to do the tag and commit.

Comment by Steven Vannelli [ 06/Oct/20 ]

jason.chan was there a particular order/process you followed with the STAR team for 4.8?

Comment by A. Jesse Jiryu Davis [ 06/Oct/20 ]

Unblocked now. For the moment, my patch builds fail because they expect the current version to be 4.9.0, but that's not true until we create an r4.9.0-alpha tag on the origin repository. This is a Catch-22: I don't want to commit until I think my change is correct, but I can't test my change very well until I commit. I'm trying some workarounds.

Comment by A. Jesse Jiryu Davis [ 02/Oct/20 ]

Blocked on some setup_multiversion_mongodb.py work to make the latest 4.8.0 build downloadable, I'll link a ticket here once we know more.

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