I'd definitely like this sort of thing.  I love Void as a distro, but I can't sanely use a rolling release distribution for my production servers without some kind of safe upgrade path, similar to how Ubuntu snapshots every 6 months.  Ideally, support short exist for security updates for a year from a patch level, me thinks.

On Monday, April 6, 2015 at 6:16:05 PM UTC-5, bougyman wrote:

  With the existence of the void daily package archive, I've been bouncing around an idea about how someone (some admin/architect/enterprise) could maintain

their own 'stable' release cycle of void. If upon initial configuration the repos are set to an archive with a date stamp, and the user has a way to validate that moving

from that datestamp to ### future datestamp doesn't (potentially) break any functionality, they can safely choose an upgrade path. for instance.

I install on 2015-03-26 and lock the repository to the archive snapshot of that date

on 2015-04-26 I run *magic-command* and ask if upgrading to current (2015-04-26) would (potentially) break any installed packages.

I get output about any important breaking changes (to xbps, etc) which may require an 'upgrade this first' action or 'remove these' actions.

I get output that may just say: 'Upgrade to 2015-04-01 first, then to 2015-04-15, then 2015-04-26' (or does this automagically?)

Thoughts?

bougy