[SERVER-70678] Bump 6.2 Created: 18/Oct/22 Updated: 07/Feb/23 Resolved: 07/Feb/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | ||
| Reporter: | Britt Snyman | Assignee: | James Hippler (Inactive) |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | branch-6.2, post-branch | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Server Release
|
||||||||
| Participants: | |||||||||
| Description |
|
When we release 6.2.0, after the final RC, we need a commit to generate a new commit hash. In addition to the bump, disable the periodic build in Evergreen (it is re-enabled during code freeze - see the code freeze placeholder ticket). |
| Comments |
| Comment by James Hippler (Inactive) [ 07/Feb/23 ] |
|
This is no longer possible now that 6.2.0 has been released. Closing Ticket. Won't Do. |
| Comment by Aaron Morand (Inactive) [ 30/Jan/23 ] |
|
For clarity on when we need to do this. It is after the last RC on the release is confirmed and we're ready to start the GA release. The bump commit should be the next commit on the branch after the last RC commit, since the GA release uses the same commit as the last RC. |