Skip to content

Spike: Evaluate the approach of delivering Slack for Self-Managed First

Investigation

As discussed in our Integrations Weekly meeting, Slack suggested some benefits to deploying to Self-Managed customers first. We can more quickly iterate, release new features to customers, and then batch larger units of value into packages to push through the Slack Approval process for .com. On our end, we could also engage internal and Beta customers who are using Self-Managed GitLab and Slack to get rapid feedback and validation as we roll out updates.

For this Spike, we'd like to evaluate the approach and identify any blockers/challenges, and if possible, set up a process or framework for development moving forward. If the team prefers .com first based on this investigation, we'll just need to come back around to figure out how to roll updates from .com to Self-Managed at a later date.

Questions

  • What's the recommended approach?
  • What will allow us to iterate and provide value to customers most quickly?
  • What is the process/documentation for rolling out updates or getting started on a new Slack feature/update?
  • What is the process for bundling up features delivered through App Manifests to Self-managed customers into GitLab.com updates?

Resources

Edited by Markus Koller