[Sorry for the resend, Coolo - accidentally sent it from my personal address] Hi Coolo - Quick question for you on how the kernel projects on the build service should be structured. I've noticed GNOME and KDE have :Factory projects, but I'm unclear on their uses. Are the GNOME and KDE projects the devel projects and the GNOME:Factory and KDE:Factory projects the bleeding edge? Is there a cascade effect where changes start in :Factory, then flow into the regular repo, and then into the openSUSE:Factory project? If that's the case, then my problem is easy enough to solve. Here's my concern. Kernel:HEAD serves two purposes which are going to conflict in the next week or so. The first is that it contains a reasonably up-to-date snapshot of the master kernel git repo. The second is that it serves as a devel project for openSUSE:Factory. In the next week, 2.6.32-rc2 will be released and that is usually when I start revving the master kernel to sync up with the latest upstream snapshot. With the current setup, that will end up putting untested and potentially unstable code in the devel project, which appears to be synced fairly frequently into openSUSE:Factory. That's not what we want, obviously. OTOH, the KOTD HEAD/master kernel has always been the bleeding edge and I don't want to change that either. We can sync the 11.2 tree to Kernel:HEAD after the split, but then we lose the testing we regularly get from having that repo. OTOH, if we add another kernel package, and use that as the devel project, then we can keep Kernel:HEAD the way it is and preserve openSUSE:Factory as well. Do you have an opinion here? Thanks. -Jeff -- Jeff Mahoney SUSE Labs -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org