[SERVER-65279] Communicate FCV Process Around backports_required_for_multiversion_tests.yml Created: 05/Aug/21  Updated: 29/Oct/23  Resolved: 13/Jun/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: Vivian Ge (Inactive) Assignee: Iryna Zhuravlova
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Backwards Compatibility: Fully Compatible
Sprint: DAG 2022-04-18
Participants:

 Description   

Description

This ticket was an action item identified from August 4th's 5.1 FCV Constants Retro: currently there is a knowledge gap surrounding the backports_required_for_multiversion_tests.yml file in regards to the upgrade/downgrade process. 

Expected Deliverable

Create and document the expectations around how SERVER teams should interact with this file, as it relates to upgrade/downgrade work. 

Expected Teams Impacted

Teams with fcv deliverables 



 Comments   
Comment by Ian Whalen (Inactive) [ 13/Jun/22 ]

iryna.zhuravlova@mongodb.com so can this be resolved?

Comment by Githook User [ 02/Jun/22 ]

Author:

{'name': 'Iryna Zhuravlova', 'email': 'irene.zhuravlova@gmail.com', 'username': 'Irsik'}

Message: SERVER-65279 Update example to include versioning
Branch: master
https://github.com/mongodb/mongo/commit/60cd74cea4e3afe7ed284fb8b3b1a6a6909d178f

Comment by Steven Vannelli [ 06/May/22 ]

iryna.zhuravlova@mongodb.com just checking in on this one. Looks like the checks have passed on the PR. Anything blocking this merge? 

Comment by Githook User [ 05/Apr/22 ]

Author:

{'name': 'Iryna Zhuravlova', 'email': 'irene.zhuravlova@gmail.com', 'username': 'Irsik'}

Message: PROG-5475 Update example to include a version

Modified the existing example to include a version as well
Branch: prog-5475
https://github.com/mongodb/mongo/commit/6c1a28c2caab3a9f31b594e203fe2732e22fea69

Comment by Brooke Miller [ 05/Apr/22 ]

Should this still be assigned to the TPM team's Backlog User, iryna.zhuravlova?

Comment by Alexander Golin (Inactive) [ 05/Apr/22 ]

Bumping to Ready for Work so it shows up on the board

Comment by Brooke Miller [ 04/Mar/22 ]

Tagging iryna.zhuravlova as Iryna supports Rob's group

Comment by Steven Vannelli [ 04/Mar/22 ]

Thanks vishnu.kaushik!

brooke.miller / robert.guo - would your team be okay with updating that example? Do we think it's helpful to add a note about it in the FCV Reference Style Guide?

Comment by Vishnu Kaushik [ 16/Feb/22 ]

I think that documentation is pretty good. Is it possible to modify the existing example by including a version as well? So instead of

# Example:
# replica_sets_multiversion:
#   - ticket: SERVER-1000
#     test_file: jstests/core/my_test_file.js

maybe

# Example to prevent 'my_test_file.js' from running in the 'replica_sets_multiversion' suite with the last-continuous binary (if that's what happens as a result, I've forgotten now)
# last-continuous:
#   replica_sets_multiversion:
#     - ticket: SERVER-1000
#       test_file: jstests/core/my_test_file.js

Sometimes as a beginner it's hard to understand without spelling everything out. If the example was complete and had all the labels I think that would be nice.

Comment by Brooke Miller [ 15/Feb/22 ]

Got it, thanks for linking to those in-line comments!

vishnu.kaushik, what do you think? Is this inline documentation here sufficient?

Comment by Robert Guo (Inactive) [ 15/Feb/22 ]

Possibly, backports are pretty nerve-wrecking. We have inline documentation here in that file but happy to elaborate anything further.

Comment by Brooke Miller [ 15/Feb/22 ]

robert.guo is this something that STM could clarify? CC iryna.zhuravlova

Comment by Vivian Ge (Inactive) [ 04/Jan/22 ]

Hi vishnu.kaushik, I remember that you were involved in our post-mortem regarding the FCV work from 5.0. I wanted to begin the communication around this, but don't have visibility into how teams should interact with this file. Is this still a ticket that needs to be done? 

If yes, please let me know what to communicate with the teams, I'm happy to work with you to send something out and find a place where this information should live. 

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