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