As a Wikibase Product Manager, I want the current version of the Federated Properties 2 feature to be deployed to a public testing environment so that users can try the feature and give feedback on the UI/UX of using Federated Properties (particularly within entity pages).

A group of users will be testing this feature out between late 2021 to early 2022. Once a tester is recruited, it should be simple for us to create a test wiki with FedProps2 enabled for their use over an approximately 2-4 week period.

Notes:

• Adding additional functionality to the FedProps 2 feature is not within scope of this story.
• Whatever we do we want to keep it as simple as possible to update things (security patches, etc.) to whatever we have deployed
• W/r/t to extensions or tools required for this testing round: nothing beyond vanilla Wikibase is required. Our main goal is to test the interactions taking place on the entity pages (items, properties)
• FedProps 2 does not include working RDF output for entities that make use of federated properties, thus error for that path are to be expected and are for now fine to have.. (This means these wikis will not fully work with the query service)

Options Considered:

1. Wikibase.dev: Take snapshot of all repos and using them at some point in time.
   • Con: Security updates of mediawiki and other extensions becomes hard OR we follow master continuously (also hard due to possible DB updates etc)
2. Wikibase.dev: Taking snapshot of Wikibase (and WB exts) but using other repos at fixed stable version (1.37 rc)
   • Pro: MW and extension security updates can be followed. DB updates mostly stable. Would still need to backport (to our snapshot) Wikibase etc security patches
3. Wikibase.dev: Backport the feature patches that we need into 1.37 in Wikibase, etc. and then continue with 1.37 everywhere
   • Pro: Set ourselves up for a 1.37 release with federated properties (if we want that). Security releases for all components work as normal. Potentially least uncertainty with future work?
4. Cloudvps: Fix the existing test system on cloudvps for testing purposes
   • Pro: Probably lowest effort
   • Con: Less investing in our future. Still a question of which code to deploy. We would need multiple test systems, potentially (as done for FedProps1).

Decision Made
Documented in T295881.