Introducing core, stable/unstable IMPORTANT asking for FEEDBACK

Jean Bruenn jean.bruenn at ip-minds.de
Sat Mar 17 14:53:46 CET 2012


On Sat, 17 Mar 2012 01:04:08 +0100
"Duncan Gibson" <duncan.gibson at xs4all.nl> wrote:

> one month seems a long time for a bleeding edge source distro, but
> then I suppose you can always download unstable, right? Agree about
> respecting or asking MAINTAINER more, but then we also need a way of
> transferring MAINTAINER if someone goes AWOL.

Keeping in mind, that some of us are crying really fast due to unstable
systems - And even more of us HAD to remove lunar from their boxes
because working was impossible with it - One month is worth it. I
wouldn't say lunar linux is a bleeding-edge-source-distro - We're
bleeding-edge because of a few developers who always want the latest
things in their system. With this one month rule they still can keep
the latest stuff in their zlocal - but normal users and devs wouldn't
be harmed (which is the goal)

> mars/stable should have the core X11 stuff, and core DE such as xfce4
> and kde. If someone would come forward to maintain the Gn*me stuff...
> 
> maybe some other key apps could be in mars/stable (languages and LAMP?
> ) but we should aim to keep it pretty slim too.

If I understood auke and the talk about git core/stable/unstable
correctly, stable and unstable are branches of mars, which means that
basically stable and unstable will contain the same software, with
most likely different versions - where as the CORE would contain only
those applications which are essential for a working environment +-
stuff which is needed for the ISO.

> One question: how to handle those core/stable modules that are
> constantly being updated? do we wait for the first update to survive
> a month before that specific version can be promoted into stable?
> what about updates, bug-fixes and security patches that might appear
> before the month is up?

That's something we should discuss about. Currently Lunar's policy is
to not use patches except they're really needed. Which is like...
never. That's because we / the devs of lunar wanted to keep lunar
"vanilla". However, if we add a patch we do so because of some
bug/problem, not to add features -> That means a patch is there for a
reason and well tested. So I'd say, security patches/bugfixes can be
applied immediately after testing.

But again, that's just my opinion.


More information about the Lunar-dev mailing list