[SERVER-65004] Make it harder to add a stable field/change a unstable field to stable in the IDL compatibility checker Created: 28/Mar/22  Updated: 29/Oct/23  Resolved: 28/Jul/22

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

Type: Task Priority: Major - P3
Reporter: Huayu Ouyang Assignee: Vesselina Ratcheva (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: Repl 2022-05-16, Repl 2022-05-30, Repl 2022-06-13, Repl 2022-06-27, Repl 2022-07-11, Repl 2022-08-08, Repl 2022-07-25
Participants:

 Description   

Currently, we allow changing an unstable field to stable or adding a stable field, but people could add/change them without fully understanding the implications of what adding a field to the stable API means (e.g. you can't ever remove that field from the stable API within this API version).

We should make it harder by creating a list similar to the existing ALLOW_ANY_TYPE_LIST that people have to add their fields to in order to allow them to be added as/changed to stable.



 Comments   
Comment by Githook User [ 28/Jul/22 ]

Author:

{'name': 'Vesselina Ratcheva', 'email': 'vesselina.ratcheva@10gen.com', 'username': 'vessy-mongodb'}

Message: SERVER-65004 Make it harder to add a stable field/change an unstable field to stable in the IDL compatibility checker
Branch: master
https://github.com/mongodb/mongo/commit/6262d18688be3abd292b01a52623cd13e7c8cd7f

Generated at Thu Feb 08 06:01:39 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.