On Wed, 2013-04-24 at 04:00 +0300, Luc Pionchon wrote: > On 24 April 2013 02:14, Florian Müllner <fmuell...@gnome.org> wrote: > > On Tue, Apr 23, 2013 at 11:09 PM, Marco Scannadinari > > <ma...@scannadinari.co.uk> wrote: > > > I think your suggestion of a "feature" branch can be a worthy > > compromise, though. > > > > Except that Bastien is right - while on a branch, a feature will > > hardly be tested by anyone than other core developers of the same > > module. It's unfortunate, but "real" users generally only get to test > > a new feature once it appears in their distro (read: some time after > > the feature appears in a stable GNOME release). > > > A branch can be packaged as well. > > So one module could have two packages.
Who will package them? For which distros? With how much delay? > One with "mature" UI changes. > One with "controversial" edge UI to be tested. Now consider the many modules forming GNOME. Do you build the "edge" package of, say, GNOME Shell against the "mature" package of GLib? Or also against the "edge" of GLib? Such a solution would quickly lead to an explosion of possible combinaisons of edge/mature packages. Unless you mean that a user must install the "edge" package for all modules if all they want is to test the "edge" of GNOME Shell? If so, how is that different from just installing the 3.9 packages in a development distro? -- Mathieu _______________________________________________ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
