Cayetano Santos <csant...@inventati.org> writes: > Let me just play the dummies advocate for a moment ...
Thank you. I believe it is important to consider such scenarios (among others). > They will be doing `whatever install guix`, and then they’ll happily > start using guix: with a bit of documentation, they’ll love it. This > is all they need to know. Don’t tell them to do a `python pull`, > `firefox pull` or `guix pull`. It comes to the same for them: they > won’t understand. Is my understanding of your scenario as summarized below correct, could you please confirm? There are some individuals who would be able to follow the instructions to install Guix. However, these individuals wouldn't understand the instructions to perform a "guix pull". Further, the number of such individuals is greater than zero, and you are proposing that we consider their needs when determining the release process for Guix. Assuming my understanding above is correct, wouldn't you agree that (even) for those individuals what's most important is that there is a _stable_ and _not-very-outdated_ release available? My (and I believe Greg's) contention is that following a time-based release process achieves these objectives more effectively than following a feature-based release process. -- Suhail
