Page MenuHomePhabricator

Define processes related to releasing (and maintaining) software not maintained by the WMDE [TIMEBOX: 4 hrs]
Closed, ResolvedPublic

Description

Likely to be split into different categories, e.g.

  • "Standard" software (e.g. Elastic search)
  • WMF owned software (e.g. Blazegraph, Query Service)
  • Community owned/Not maintained software (e.g. Quick Statements)

Aspects to possibly cover (list incomplete)

  • When these are updated to new versions
  • What are WMDE's responsibilities in maintaining (e.g. fixing bugs, security issues) in these

Event Timeline

WMDE-leszek renamed this task from Define processes related to releasing software not maintained by the WMF to Define processes related to releasing (and maintaining) software not maintained by the WMDE.Jan 20 2021, 8:20 PM

To potentially include in the task:

  • Document publicly WMDE's maintenance responsibilities (i.e. very limited ones, only in the context of the Wikibase suite release packages) for non-WMDE maintained software components
  • Decide on how new versions of non-WMDE software components (including security fix releases) are going to be included in the releases of Wikibase suite (e.g. in what cases new versions Wikibase release packages will be published) and document it for the internal use of the WMDE team
  • Refer to the documentation of the security releases in the context of the non-WMDE-maintained software (T272582).

Timebox: 4 hours

WMDE-leszek renamed this task from Define processes related to releasing (and maintaining) software not maintained by the WMDE to Define processes related to releasing (and maintaining) software not maintained by the WMDE [TIMEBOX: 4 hrs].Apr 27 2021, 8:01 AM

My thoughts:

  • No commitment to write patches to any non-WMDE software
  • Commit to produce new wmde.N release when a component has a significant security release that effects it's usage in the suite
  • Process is new ticket in campsite following the normal process for insecure dependencies
  • Commit to create phabricator tickets for projects maintained on phabricator if none exist
  • Direct users to make their own tickets for upstream bug reports (e.g. to elasticsearch)