I think frequent releases and frequent binaries are important for some kinds of users, but I’ve become convinced that at least right now most core developers of the science pipelines stack are better off just building everything from source and updating that stack in-place frequently, and what we should be providing are better tools to do that.
Everyone I know who is not building from source (and instead tries to mix-and-match master packages with released versions) seems to encounter a nonexistent bug or segfault (actually just a version incompatibility) at least once a month. Those don’t just slow down the developer who ran into the problem; they distract everyone else who helps try to reproduce and debug the problem. And while frequent releases will make that less of a problem, I don’t think it will go away anytime soon; there’s simply too much churn. Moreover, installing new releases frequently will either force users to delete old releases frequently or deal with the EUPS sluggishness that comes from having too many versions and tags. And on the other hand, I think the idea that developers need to have a lot of tagged versions on hand to reproduce bugs reported specifically in those versions simply hasn’t materialized (at least not yet). Finally, it makes developers self-sufficient: if they can build everything themselves just as easily as they can ask someone in e.g. SQuaRE to do it, they can’t have their work blocked by SQuaRE availability or CI downtime.
A lot of those problems with building against releases are problems that will have to get fixed anyway: lower-level packages will stabilize, EUPS performance will be improved, improved CI automation will reduce human-availability blockage. But we’ve been struggling to solve this problem by having more frequent releases for years now, and we’ve put very little effort into build-the-stack-from-source tools for developers, and essentially abandoned the effort we have done (lsst-build and lsstsw) to “use at your own risk; this was intended for CI”. There might be a faster solution to the new developer problem there.