Jump to content

Portal:Toolforge/Ongoing Efforts/Toolforge Workgroup/Reports/FY2024-2025/OKR/6.3.10 Push-to-Deploy Beta Release

From Wikitech

Description

By creating a beta release of the push-to-deploy workflow for toolforge, we will validate the current direction and features and make sure they align with the user needs before declaring them stable.

Phabricator task: https://phabricator.wikimedia.org/T393564

Final Update

Summary

On the hypothesis of starting a beta process for the push-to-deploy features:

The hypothesis has not yet been proven, today is the start of the beta, though with high certainty we can say that all the systems for the minimal set of features for beta are in place.

We have setup already 4 tools in production that have done >30 deployments in preparation for the beta. The minimal features implemented already reduce 10% the number of tasks to do to deploy a tool (see the canonical test tool https://sample-complex-app.toolforge.org), and will see a considerable extra reduction soon.

For this hypothesis we created a plan for the beta, including selecting the minimal user flows that would make it. As part of the execution of that plan:

  • We developed, merged and deployed all the minimal features and bugfixes.
  • Created a feedback loop for users to communicate feedback, new features, bugs, ...
  • Created the Admin documentation and operational infrastructure to support the service at production level
  • Created user documentation and tooling for new users to get started using the service.

Major lessons

During this quarter we were really stretched on resources, and probably the major lesson here would be to make sure that that is communicated effectively, and avoid overworking even if that means not delivering the hypothesis.

Product-wise, having a clear list of features/user-flows needed for the beta help enormously prioritize. Next time would be nice to have product management input too (we are getting one for the project), but it's a great tool anyhow.

Next steps

Next steps is to follow up the beta process, gather feedback, and deliver the missing features to stabilize the service (all described in the beta document and task).

Retrieved from "https://wikitech.wikimedia.org/w/index.php?title=Portal:Toolforge/Ongoing_Efforts/Toolforge_Workgroup/Reports/FY2024-2025/OKR/6.3.10_Push-to-Deploy_Beta_Release&oldid=2319238"