On 06/15/2016 07:20 PM, Jim Fehlig wrote: > On 06/15/2016 06:42 AM, Pavel Grunt wrote: >> Hi, >> >> On Tue, 2016-06-14 at 23:40 +0200, Fabiano Fidêncio wrote: >>> These small series has as objective start "preparing the ground" for >>> the work Sagar Huge has been done on re-design/re-write virt-viewer's >>> UI in a way to have it looking as something from this decade. :-) [0] >> I really like the new UI. >>> There is still a lot of work to do on our (Sagar's and mine) side and >>> once they are fixed he will send the patches and ask for comments and >>> reviews. So far I'm keeping his patches rebased on top of current >>> master on my personal gitlab[1] and you also can find his work on his >>> personal's github[2]. >>> >>> As I said, there's still a lot of work to do and we are trying to do it >>> as soon as possible. Our target is to have it in for Fedora25 and maybe >>> we will need a virt-viewer release before starting, actually, doing the >>> UI changes (for those who want to stick to the old UI/not bump GLib/Gtk >>> dependencies' versions). >> F25 sounds like a reasonable goal >> >>> This small series of patch can also be found on another branch of my >>> personal gitlab repo[3] and can be waiting there till we have SLES 12 >>> SP2 release, as the 3rd patch of this series will bump GLib dependency >>> version, making impossible to build virt-viewer in a stock SLES 12 SP1. > > That's a bummer, but... > >> I don't think it is reasonable to wait for SLES to be released. > > agree that upstream development shouldn't come to a halt due to an old version > of glib in SLES12 SP1. For the record, here are glib versions in relevant SUSE > distros > > openSUSE 13.2 (becoming rather old openSUSE release): 2.42 > openSUSE Leap 42.1 (latest stable openSUSE release): 2.44 > openSUSE Tumbleweed (rolling openSUSE release): 2.48 > SLES12 SP1 (latest stable enterprise release): 2.38 > SLES12 SP2 (enterprise release scheduled for Oct 2016): 2.48 > >> As you said a >> release can be done before merging Sagar's and yours works upstream. > > Ah, so there will be a release before these changes go in? And a release with > the changes isn't planned until later in the year, e.g. October or later? If so, > the latest release will always work with the latest SUSE Linux Enterprise. Only > developers would be affected, but they should be using something newer anyhow. > I think this is a good plan. Release first and then bump requirements for the next one. -- Eduardo de Barros Lima (Etrunko) Software Engineer - RedHat etrunko@xxxxxxxxxx _______________________________________________ virt-tools-list mailing list virt-tools-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/virt-tools-list