stable branch

[Duncan Gibson]

> I wonder whether it would make more sense to combine the stable branch
> idea with sofar's split moonbase idea, so that the stable branch only
> has to concentrate on a limited number of modules to start with.
>
> The current 'unstable' moonbase modules would still be updated as now,
> and available as a fallback repo if a user wanted a module that had not
> been tested and added to the stable branch.
>
> I don't know how easily this could be handled in lunar/theedge but I
> thought I would throw the idea into the discussion.

And just to reflect something that has been mooted several times before,
and which might address the problems in the "zdeprecated: cleanup" thread,
if we could replace "lin moonbase" with something that would also send
the current "lvu installed" list to doppio so that we could see which
packages were really being used, we could concentrate our efforts better.
Maybe someone could generate a graphical web page showing module usage.
Of course the stats would be as anonymous as possible (download machine
sha1sum or something) and would only be valid for a year or similar.

We could extend the idea so that the current 'unstable' moonbase is not
just a fallback repo but also zdeprecated as well, and if the installed
stats showed enough current users of an unstable/zdeprecated module then
we would make it stable, or at least discuss what to do with it.
People using zdeprecated module would do so at their own risk.

Just another 2 eurocents
D.