[gentoo-dev] Re: Baselayout 2 stabilisation todo
Hi, Doug Goldstein car...@gentoo.org: On Fri, May 22, 2009 at 5:17 AM, Christian Faulhammer fa...@gentoo.org wrote: Hi, I'd like to collect some things we need to do before Baselayout 2 and OpenRC can go stable. Up to now I have: * eselect 1.1 stable (current RC3) for the support in the rc module * a newer splashutils stable * documentation updates (http://bugs.gentoo.org/213988, thanks Jeremy) What else? As some of you might foresee, this can be as hard as a major GCC stabilisation, so it must be well-planned and organised. V-Li -- Christian Faulhammer, Gentoo Lisp project URL:http://www.gentoo.org/proj/en/lisp/, #gentoo-lisp on FreeNode URL:http://gentoo.faulhammer.org/ The only reason why OpenRC has not come up for stabilization by it's maintainers is the fact that everytime there's a new version readied for release, on the horizon there's new incompatible changes being planned for the next version. The OpenRC maintainers in Gentoo have always chosen to wait until OpenRC settles down a little bit. Now with the plan to drop support for certain features (ADSL and PPP support in the networking code), it's going to rewrite more Gentoo people to step up to develop and maintain this code. After having seen vapier speaking about stabilisation on -core we had a discussion about the wanted news item, which i posted for review. Before the todo mail, I wrote to the maintainers (Roy and base-system) some days in advance, with only a reaction from Roy. If you're volunteering for this position, Christian, I'll happily step down and allow you to maintain this. I would also discuss this with zzam and vapier, the other 2 maintainers of OpenRC. All I want to do is help with the stabilisation...which I though is nigh. V-Li -- Christian Faulhammer, Gentoo Lisp project URL:http://www.gentoo.org/proj/en/lisp/, #gentoo-lisp on FreeNode URL:http://gentoo.faulhammer.org/ signature.asc Description: PGP signature
[gentoo-dev] Re: Baselayout 2 stabilisation todo
Hi, Roy Marples r...@marples.name: If there is a real drive to make OpenRC stable then I suggest that I roll openrc-0.5.0 out sometime this week and try to roll rc events into 0.6.0, the embedded stubs into 0.7.0 and we'll go from there. Sounds fine to me. I don't want to press anything, just some kind of plan would be fine so we can work towards a goal. I know that Cardoe has been busy in RL of late and I've never pressed or been pressed into considering it stable. However, real bug reports and new feature implementations have slowed somewhat, so either it's Ready For Stable or no-ones using it. I am using it productively on many systems even before the split-off to OpenRC. And bringing such a crucial piece of software to stable is a hard task. I have some experience in working with the surroundings from some GCC stabilisations so I can lend a hand here and be a pathfinder in stableland to prepare everything there. V-Li -- Christian Faulhammer, Gentoo Lisp project URL:http://www.gentoo.org/proj/en/lisp/, #gentoo-lisp on FreeNode URL:http://gentoo.faulhammer.org/ signature.asc Description: PGP signature
[gentoo-dev] Re: Baselayout 2 stabilisation todo
Christian Faulhammer fa...@gentoo.org posted 20090522121717.19049...@gentoo.org, excerpted below, on Fri, 22 May 2009 12:17:17 +0200: I'd like to collect some things we need to do before Baselayout 2 and OpenRC can go stable. Up to now I have: * eselect 1.1 stable (current RC3) for the support in the rc module * a newer splashutils stable * documentation updates (http://bugs.gentoo.org/213988, thanks Jeremy) What else? As some of you might foresee, this can be as hard as a major GCC stabilisation, so it must be well-planned and organised. What about the deprecated reliance on the old-style addons code as used by at least the mdraid (mdadm package) and lvm (lvm2 package) services? (I'd quote except the messages don't appear to be logged so I can't get 'em without rebooting.) I've not filed a bug as I'm sure the maintainers can read as well as I can, but if we're talking about stabilizing openrc, getting them in shape and stable without dependence on already deprecated functionality so stable users never see that warning would be nice. Such warnings tend to be (generally unnecessarily) alarming to normal users, especially when a brand spanking new upgrade is already emitting deprecated warnings. Or should I file the bugs? It seems no one else has and maybe the maintainers don't have the config for what they're maintaining, or otherwise don't see the warnings. -- Duncan - List replies preferred. No HTML msgs. Every nonfree program has a lord, a master -- and if you use the program, he is your master. Richard Stallman
Re: [gentoo-dev] Re: Baselayout 2 stabilisation todo
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Duncan wrote: Or should I file the bugs? It seems no one else has and maybe the maintainers don't have the config for what they're maintaining, or otherwise don't see the warnings. I'm aware of the dm-crypt issue and will try and spend some time this weekend getting that into shape. If you do file bugs, please make them block bug 251730 [1], which is the deprecated warning tracker. Thanks... Mike 5:) [1] http://bugs.gentoo.org/251730 -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.11 (GNU/Linux) iEYEARECAAYFAkoWoI8ACgkQu7rWomwgFXo0UgCeKTtnrZAR0y8rIdNSDOJRje1w F5MAoKr1jJIM/JtBJL+ibxmzkFIV96lB =AyNP -END PGP SIGNATURE-
[gentoo-dev] Re: Baselayout 2 stabilisation todo
Mike Auty ike...@gentoo.org posted 4a16a08f.8060...@gentoo.org, excerpted below, on Fri, 22 May 2009 13:54:39 +0100: I'm aware of the dm-crypt issue and will try and spend some time this weekend getting that into shape. If you do file bugs, please make them block bug 251730 [1], which is the deprecated warning tracker. Thanks... ... And to think of all the time I just spent looking for mdadm and lvm2 bugs and missed that one! Thanks. I couldn't believe there weren't bugs on it at this late stage, but I sure couldn't see 'em. CCed. -- Duncan - List replies preferred. No HTML msgs. Every nonfree program has a lord, a master -- and if you use the program, he is your master. Richard Stallman
