[SERVER-58832] Update signing key to 5.2 in master Created: 26/Jul/21  Updated: 06/Dec/22  Resolved: 27/Jul/21

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

Type: Task Priority: Major - P3
Reporter: Vivian Ge (Inactive) Assignee: Backlog - Build Team (Inactive)
Resolution: Won't Do Votes: 0
Labels: branch-5.1, during-branch
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-41224 Update signing key to 4.4 in master Closed
Assigned Teams:
Build
Participants:

 Description   

After branching the new version, master should use the next version's signing key.\\\\ This can be doen before the branch, as long as we select a branch point before the commit on mainline.



 Comments   
Comment by Vivian Ge (Inactive) [ 27/Jul/21 ]

Thanks, April! Updating my template with this information now. 

Comment by April Schoffer [ 27/Jul/21 ]

This isn't needed for quarterly releases. We'll use the 5.0 signing key until 6.0

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