This email is mostly for Swift and gizmo, but anyone can have their input. I've been running a SELinux system for the last month or so since I've uploaded the massive work done by Swift and gizmo. There was one major bug we noticed right away, and Swift got it, namely bugs #355745 and #356533 --- dups. After that, it looks pretty clean.
I'm think we should go for stabilization --- I'm not sure how since the arch teams are going to say they really can't test this for us, and as they did with other packages, will probably defer the judgment back to us. If we do, we should take this responsibility very seriously because the arch teams, if nothing else, are a double check on our work. So far I see only a few bugs that need addressing still in bugzilla. (The bug reports are a bit disorganized because of how they were assigned. We're going to be assigning selinux bugs to [email protected] for easy lookup.) I think these are blockers to stabilization. Any others you want to add to the list? #355675 - No brainer. I'll test the patch there this afternoon and put it on the tree later if it works. #346563 - sounds like a profile problem, but I'm not sure its valid -- Anthony G. Basile, Ph.D. Gentoo Developer
