James Ogley wrote:
And should we continue with 2.19 in Factory or continue there with 2.18? What do you think?
Will we get 2.20 in time for 10.3?
I think I've suggested it before but maybe G:U could have a Factory target added so we (in this instance) stick with 2.18 in Factory so that we have a stable GNOME release in 10.3 and start building 2.19 in G:U. Then, once 10.3 is released, import the work from G:U into Factory and disable the Factory target on it until the next GNOME development cycle comes around.
Nice idea, but hard to realize. We need a NO-GO flag for SuSE Autobuild/Factory, otherwise people will modify tens or hundreds of packages in Factory with a lot of minor patches and somebody have to spent several days or weeks with reviewing them and merging when 2.20 will come. I remember this problem from December, when I did /opt/gnome -> /usr move. Proposal: NO-GO package will have a .buildservice file in its repository. .buildservice will contain a string with BS project and package name, where it is maintained. More lines mean, that more versions are maintained. Autobuild team will reject manual updates of these files. -- Best Regards / S pozdravem, Stanislav Brabec software developer --------------------------------------------------------------------- SUSE LINUX, s. r. o. e-mail: sbrabec@suse.cz Lihovarská 1060/12 tel: +420 284 028 966 190 00 Praha 9 fax: +420 284 028 951 Czech Republic http://www.suse.cz/ -- To unsubscribe, e-mail: opensuse-gnome+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-gnome+help@opensuse.org