Explicitly document the lack of an update path

[phenaproxima]

Starshot has no update paths, crossgrade paths, or migration paths for anything. That is not within its scope or its mission.

When you start a project with Starshot, you get the best starting point we can offer, at that time. Best practices may evolve, but Starshot is NOT responsible for keeping you up-to-date. Modules can provide update paths for their own data, but that's not something Starshot will do on their behalf. Distributions, by contrast, have traditionally tried to do this by various means, but Starshot is not a distribution and shouldn't be expected to act like one.

I think that we should explicitly and clearly document this decision and the rationale behind it, right in our README, so that we have somewhere to point people when this question comes up.

All that being said, if a best practice emerges around managing config updates (like the Update Helper module), then I wouldn't be against Starshot including that as an endorsement for site maintainers who need to do config updates. But it should never be expected that Starshot will provide update paths.

[simesy]

I agree and it's mostly about awareness, so just an agreement form/layover?

[simesy]

... or just promote the Upgrade Manager.