[SERVER-47655] Request to leverage IDL to ease tracking of server parameter changes Created: 20/Apr/20 Updated: 05/Dec/22 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | IDL |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Maria van Keulen | Assignee: | Backlog - Server Release Team |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Assigned Teams: |
Server Release
|
||||
| Participants: | |||||
| Description |
|
Presently, with each MongoDB release, we create an internal document in which we note all parameter and configuration changes since the previous release. This process includes manually reviewing changes to IDL files and copy/pasting the necessary information to the document. Our process would be more efficient if IDL could be leveraged somehow to automatically generate a document with changes, given that in many cases the information in the IDL files is used verbatim--albeit with some formatting changes. |
| Comments |
| Comment by Lauren Lewis (Inactive) [ 21/Dec/21 ] |
|
We haven’t heard back from you in at least 1 year, so I'm going to close this ticket. If this is still an issue for you, please provide additional information and we will reopen the ticket. |