A rolling release model should not be confused with a staged or "staggered" rollout, in which an update is gradually made available to an increasing percentage of users for testing or bandwidth reasons.
Some modern Distributed SQL databases such as YugabyteDB also support this feature.
A rolling release is typically implemented using small and frequent updates.
However, simply having updates does not automatically mean that a piece of software is using a rolling release cycle; for this, the philosophy of developers must be to work with one code branch as opposed to discrete versions.
When the rolling release is employed as the development model, software updates are typically delivered to users by a package manager on the user's personal computer, accessing through the internet a remote software repository (often via a download mirror) stored on an internet file server.