Let's have a meeting to discuss use cases and decide a way forward for sharing the same group of articles on our dev instances.
Duration: 1hr
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Declined | • Jhernandez | T104317 [GOAL]: Release process and staging environment | |||
| Resolved | • Jhernandez | T100296 [EPIC] Create a formal release process for MobileFrontend/Gather | |||
| Declined | • Jhernandez | T104324 [EPIC] Create a development staging environment and branch. | |||
| Declined | Jdlrobson | T104556 Merge to development branch on MobileFrontend by default | |||
| Resolved | • Jhernandez | T104559 Setting up staging is reproducible by engineers | |||
| Resolved | phuedx | T104558 Set up a staging environment for development | |||
| Resolved | bd808 | T104994 Staging environment for Reading Web | |||
| Resolved | Jdlrobson | T113972 Switch Gather development to dev branch | |||
| Duplicate | None | T105733 Establish corpus of pages to be used for testing | |||
| Declined | None | T104561 Gather a set of sample articles to load on test/staging instances. | |||
| Resolved | Jdlrobson | T107770 Spike: Identify the best way forward for including sample articles in Vagrant |
Event Timeline
Comment Actions
Had a great chat with the guys in #wikimedia-releng (thanks @bd808 @Tgr and @dduvall)
Have updated https://phabricator.wikimedia.org/T104561 with implementation notes.
The summary is the role will just be a list of titles
When provisioning we'll pull these titles from their corresponding projects and run them through the templates=expand API
Comment Actions
I'll come back to T104561 https://phabricator.wikimedia.org/T104561 next
week when planning next sprint and will probably drop it in for 54 if it is
clear enough :) Thanks @Jdlrobson! <3