-
Type: Task
-
Resolution: Duplicate
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Replication
In the 5.0 release, we ran into occasional issues where generic FCV constants were used instead of real FCVs. For these cases, we should investigate any improvements to help engineers from accidentally stumbling into this error. We currently require any generic FCV usage to have a corresponding comment that begins with “(Generic FCV reference):”. One suggestion is to expand that comment to start with:
(Generic FCV reference): This FCV reference must remain across binary version releases because…
So that it is clear that this reference must persist across releases. We could also consider renaming “generic” terminology to be more representative of their use cases.
- is related to
-
SERVER-60214 Make improvements in generic FCV commenting/terminology
- Open