On 2010-12-02 08:55:24 (+0100), Vincent Untz
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.
Ok, now I see your point.
But it is quite specific to GNOME components (and certainly fits a few
other projects), as with most upstream projects there is no specific
split between "unstable" and "stable" branches.
You often have beta versions and such, and those would _not_ be pushed
to Tumbleweed (at least as far as my understanding goes :)), but when
the next stable release is provided by upstream, we do push it to
Tumbleweed.
Of course, GNOME (and it also applies to KDE, if I'm not mistaken) is
a pretty huge chunk of packages :)
cheers
--
-o) Pascal Bleser