Post #2751354
2026-03-29 09:48 UTC
@mandrasch@social.tchncs.de not a craft user either, but ran point on many customer targeted website development projects. In the end what made the most sense for staging was to combine features into one release. Staging in the end is meant as a last review environment for the client, not the developers. Allowing your clients to aok on the staging branch before being released reduces complexity and retains cyclic development patterns.
This also means you only need one staging environment, hence forge or cicd
Replies (1)
-
@mandrasch@social.tchncs.de 2026-03-29 09:59
@luceos@fosstodon.org thanks for the insights - interesting! 👍 👍 that was pre-AI-agent era, right? (My experimental goal is to also include AI agents for the first iteration, but I need automatic preview deployments first. But that's just my side project scope, not real-world-project reasoning. :) I'll might release a demo repo soon)