[SERVER-64837] Update signing key to 6.1 in master Created: 23/Mar/22 Updated: 06/Dec/22 Resolved: 12/Apr/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Steven Vannelli | Assignee: | Backlog - Build Team (Inactive) |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | branch-6.0, during-branch | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Build
|
||||||||
| Participants: | |||||||||
| Description |
|
After branching the new version, master should use the next version's signing key.\\\\ This can be done before the branch, as long as we select a branch point before the commit on mainline. |
| Comments |
| Comment by Steven Vannelli [ 01/Jul/22 ] |
|
zakhar.kleyman@mongodb.com should this ticket be generated for the X.3 branching to tag the new major release once it becomes master? |
| Comment by Zakhar Kleyman [ 12/Apr/22 ] |
|
6.1 is a rapid release so it's going to be using the 6.0 signing key. |