[DOCS-15172] Make the Driver Compatibility Matrices more obvious in their support for connecting to "unsupported" versions Created: 14/Mar/22  Updated: 29/Jan/24  Resolved: 30/Aug/22

Status: Closed
Project: Documentation
Component/s: drivers
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Alex Bevilacqua Assignee: Mike Woofter
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
related to DOCS-15534 Update mongodb-compat tables in docs-... Closed
Participants:
Days since reply: 1 year, 23 weeks, 2 days ago
Story Points: 2

 Description   

Customers raise questions as a result of supportability for new versions of MongoDB from "older" drivers (such as https://www.mongodb.com/community/forums/t/mongodb-5-0-support-in-mongocxx/152102).

This is due to the compatibility matrices not clearly identifying that older drivers "can still connect and interact with this version but newer features would not be supported". For example in https://docs.mongodb.com/drivers/cxx/#compatibility, the C++ driver doesn't show ANY support for MongoDB 5.0, which is confusing to customers.



 Comments   
Comment by Mike Woofter [ 29/Aug/22 ]

Ruby PR: https://github.com/mongodb/mongo-ruby-driver/pull/2603

Comment by Mike Woofter [ 16/Aug/22 ]

spencer.brown@mongodb.com The compat tables for Node, Java, and Go are stored in different repositories and will have to be updated separately. We have been tracking this with these tickets:

  • DOCSP-24482
  • DOCSP-24483
  • DOCSP-24481 [completed]

The Ruby driver's compat tables are here:

https://www.mongodb.com/docs/ruby-driver/current/reference/driver-compatibility/

I've created ticket DOCSP-24617 to update them.

For the C++ tables, could you elaborate on what needs to be added or changed?

 

Comment by Nathan Leniz [ 21/Jul/22 ]

alex.bevilacqua@mongodb.com Not at all. This ticket was closed erroneously. Re-opening.

Comment by Alex Bevilacqua [ 21/Jul/22 ]

nathan.leniz@mongodb.com was the decision to just not action this? Commercial support continues to receive cases from customers concerned that they may have issues as a result of their driver showing as "not compatible" with their version of MongoDB

/cc rachelle.palmer@mongodb.com

Comment by Nathan Leniz [ 03/May/22 ]

Apologies for not adding that detail. We plan to push the legacy versions to this page.

We've also been experimenting slightly with the icons. If this is acceptable, we'll add a note to each compat table to look at the legacy page if they don't see their version. We'll also update the "About compatibility" page to reflect the new iconography.

Comment by Bernie Hackett [ 03/May/22 ]

I also prefer 3. Are we pushing "legacy support" to a matrix somewhere else, or just no longer documenting the world before MongoDB 3.6?

Comment by Alex Bevilacqua [ 03/May/22 ]

nathan.leniz@mongodb.com Option #3 looks good to me (just my 2 cents) as you can quickly verify that "your app should still be able to connect", which is the recurring question from customers we want to answer.

Comment by Nathan Leniz [ 03/May/22 ]

bernie@mongodb.com We've done some brainstorming and I've mocked up a few different approaches.

One thing we'd like to avoid is communicating information through colors since it presents an immediate accessibility issue. Looking at the different mocks, I'm also starting to worry that the tables might be too busy?

1
2
3

Do you and the DBX folks have a strong preference here?

Comment by Bernie Hackett [ 18/Mar/22 ]

I like that idea. Let me figure out how to make it happen and get back to you next week.

Comment by Nathan Leniz [ 17/Mar/22 ]

behackett These tables cause a lot of churn for us. I like your idea, and would like to propose an addition to it. When a new server version is released, could we get an update from each team on what features are not supported? Then we can add the asterisk as well as enumerate what new features aren't supported.

Comment by Bernie Hackett [ 15/Mar/22 ]

For drivers (any driver) that haven't released explicit support for a particular server release could we just use the last driver version number as the compat release with an * next to the version and have the * refer to a disclaimer that says something like "This driver version is tested against this server release but may not support all of its features" or something like that? We can go back and retroactively change the driver version number once a release with explicit support happens.

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