Le mercredi 01 décembre 2010, à 14:05 -0800, Greg KH a écrit :
On Wed, Dec 01, 2010 at 09:18:57AM +0100, Vincent Untz wrote:
One other thing I'm worried about is that this might result in some contributors focusing on the rolling update, and some others focusing on the "usual" release. Ideally, people would work together, and on both, but that's "ideally", and things will be different. So that literally splits our effort.
I don't see "contributors" having to do any different work here. They should be creating packages for Factory today, which is where the packages for Tumbleweed will come from, just after that same contributor deems them "stable" enough.
That's the simple workflow. But let's take glib as an example (you can replace glib with any other package). Factory will have a development version of glib for a while, and my understanding is that it's not what we want in Tumbleweed. For Tumbleweed, we'll instead want to push updates from the stable glib branch. So the glib maintainers will have to "actively develop" two branches of the package. This is what is behind the concern I raised. I'm not too much worried about this for my packages since it turns out I'm part of a bigger team that works rather well. I'm more worried about packages that don't have a lot of people working on them but that are still important on your system. For those packages, it might be that people will choose to focus on the regular releases, or on Tumbleweed. But again, let's not block on this. It'll be easier to fix once we actually see how much of an issue it is. Vincent -- Les gens heureux ne sont pas pressés. -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org