Page MenuHomePhabricator

[Federated Values] How to distribute Alpha release
Open, Needs TriagePublicSpike

Description

Goal
Initial investigation - Understand what changes are needed to the existing Docker release pipeline to support a separate distribution for the Federated Values, and produce a concrete breakdown of follow-up implementation tasks or suggest an alternative way to distribute the feature - either on existing Wikibase instances or fresh installations.

Context
We have a working first version of the Federated Values feature as an unmerged patch on Gerrit. We want early adopters to be able to use this feature in real environments using a standard Docker setup.

Recommended path: https://docs.google.com/document/d/1wX5CEAtfZFoIhkZ6M1tUS1kVViyWb4edR5dPYY_xVbo/edit?usp=sharing

AC

  • A breakdown of follow-up tasks to implement the distribution via our release pipeline

Details

Other Assignee
Jacob_WMDE

Related Objects

Event Timeline

Leif_WMDE changed the subtype of this task from "Task" to "Spike".
Leif_WMDE renamed this task from [Federated Values] How to package experimental release to [Federation] How to distribute Alpha release.Mar 27 2026, 5:19 PM
Leif_WMDE updated the task description. (Show Details)
Leif_WMDE changed the subtype of this task from "Spike" to "Task".Apr 9 2026, 7:32 AM
Leif_WMDE changed the subtype of this task from "Task" to "Spike".Apr 9 2026, 3:51 PM
Leif_WMDE updated the task description. (Show Details)
Leif_WMDE added a subscriber: adee_wmde.
Leif_WMDE renamed this task from [Federation] How to distribute Alpha release to [Federated Values] How to distribute Alpha release.Thu, Apr 16, 8:29 AM

Update 20.04:
Given the limited scope of the alpha release, which is intended to collect initial feedback from interested users, we want to consider a simple way to package and distribute it. Specifically, we're looking into switching development to a separate branch based on the MW release we're targeting, which the release pipeline could check out and run on manually. If this is feasible, we'll check exactly what needs to change on the release pipeline side, but we expect to avoid an extra deploy release.