6:37 a.m.
Please, take my boldness lightly but I'm already expecting
http://mail.xfce.org/pipermail/xfce/2012-December/031768.html
http://mail.xfce.org/pipermail/xfce/2012-December/031769.html
appear in updates-testing ;-)
10:54 a.m.
Am Montag, den 03.12.2012, 10:37 -0200 schrieb Sergio:
Please, take my boldness lightly but I'm already expecting
http://mail.xfce.org/pipermail/xfce/2012-December/031768.html
http://mail.xfce.org/pipermail/xfce/2012-December/031769.html
appear in updates-testing ;-)
Two remarks:
1. Please don't *expect* something unless you do it yourself.
2. I am not the new version will hit F17. It's a change of the user
experience that violates our update policy [1] and it missed
beta freeze, so I am not even sure we could bring it to F18.
Here is my suggestion:
F17: Probably not.
F18: Lets deliver it as a 0-day update, to minimize the change of the
user experience. Otherwise we'll have to support Thunar 1.4 till the F18
EOL and by that time, 1.8 will probably be out already.
Questions or comments?
Kind regards,
Christoph
[1] https://fedoraproject.org/wiki/Updates_Policy
12:34 p.m.
On 12/03/2012 02:54 PM, Christoph Wickert wrote:
Am Montag, den 03.12.2012, 10:37 -0200 schrieb Sergio:
> Please, take my boldness lightly but I'm already expecting
> http://mail.xfce.org/pipermail/xfce/2012-December/031768.html
> http://mail.xfce.org/pipermail/xfce/2012-December/031769.html
> appear in updates-testing ;-)
Two remarks:
1. Please don't *expect* something unless you do it yourself.
I can't (not for official repo, for sure). It was just a heads up as
it's supposed to be an update with incremental features and bug fixes
still for Xfce 4.10.
2. I am not the new version will hit F17. It's a change of
the user
experience that violates our update policy [1] and it missed
beta freeze, so I am not even sure we could bring it to F18.
I meant for F18. Have you tested it (I was about to build it here)?
AFAIK, it just *adds* tab support but you know Nick Schermer is very
sensible in this respect of not changing previous behaviour.
Plus it seems it solves many bugs (and it would be very welcome, like
the one that fails to show gvfs mounts on the side-bar - not sure if
it's fixed but I'll check).
Here is my suggestion:
F17: Probably not.
F18: Lets deliver it as a 0-day update, to minimize the change of the
user experience. Otherwise we'll have to support Thunar 1.4 till the F18
EOL and by that time, 1.8 will probably be out already.
Questions or comments?
You know better about these things. I'll test it here and report back.
But why would Thunar 1.4 have to be supported after the update?
Kind regards,
Christoph
[1] https://fedoraproject.org/wiki/Updates_Policy
2:02 p.m.
Christoph Wickert wrote:
Am Montag, den 03.12.2012, 10:37 -0200 schrieb Sergio:
> Please, take my boldness lightly but I'm already expecting
> http://mail.xfce.org/pipermail/xfce/2012-December/031768.html
> http://mail.xfce.org/pipermail/xfce/2012-December/031769.html
> appear in updates-testing ;-)
Two remarks:
1. Please don't *expect* something unless you do it yourself.
2. I am not the new version will hit F17. It's a change of the user
experience that violates our update policy [1] and it missed
beta freeze, so I am not even sure we could bring it to F18.
I don't
think, that we should apply to strict rules to ourselves here. I
mean the update policy is violated most of the time and I am not sure if
the user-experience is that much of a big issue. I mean a person who
could install fedora and uses xfce is most likely to adopt to changes
also during release time, especially since it's not the only change
which might happen.
Also I am not sure if user-experience is more important than let's say
fixed bugs etc.
Just my opinion.
-Johannes
Here is my suggestion:
F17: Probably not.
F18: Lets deliver it as a 0-day update, to minimize the change of the
user experience. Otherwise we'll have to support Thunar 1.4 till the F18
EOL and by that time, 1.8 will probably be out already.
Questions or comments?
Kind regards,
Christoph
[1] https://fedoraproject.org/wiki/Updates_Policy
_______________________________________________
xfce mailing list
xfce(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/xfce
3:27 p.m.
Hi,
On Mon, 03 Dec 2012 17:54:32 +0100
Christoph Wickert wrote:
Am Montag, den 03.12.2012, 10:37 -0200 schrieb Sergio:
> Please, take my boldness lightly but I'm already expecting
> http://mail.xfce.org/pipermail/xfce/2012-December/031768.html
> http://mail.xfce.org/pipermail/xfce/2012-December/031769.html
> appear in updates-testing ;-)
Two remarks:
1. Please don't *expect* something unless you do it yourself.
2. I am not the new version will hit F17. It's a change of the
user experience that violates our update policy [1] and it missed
beta freeze, so I am not even sure we could bring it to F18.
Yeah, and
still firfox gets updated mid release whenever new major
release is out (I wonder when it last broke gxine build, not to
mention it actually working :()...
<OT> speaking of which, is there any kind soul that would be willing to
take care of gxine? I've asked a couple of times for comaintainers on
-devel, but always without answers. It's a highly problematic package,
often FTBS due to changes in XUL's javascript and I'm not able to fix
those properly myself, but I recall it used to be on xfce or
lxde spin. It's a heart issue (it was my first package ever), but I'm
starting to consider dropping it, as maintaining it properly is beyond
my skills/time and morever I don't use it anymore (all hail mplayer2).
Upstream isn't dead, but terribly slow with adapting to new XUL, so
you'd have to fix those issues yourself :(
</OT>
Here is my suggestion:
F17: Probably not.
*cough-cough* What about the xfce-4.10 repo?
F18: Lets deliver it as a 0-day update, to minimize the change of
the
user experience. Otherwise we'll have to support Thunar 1.4 till the
F18 EOL and by that time, 1.8 will probably be out already.
Seems sane to me to do
the 0-day update, definitely better than having
to support 1.4 till F18 EOL ourselves.
I'm going to test it myself to see how big the changes in UI are, then
I'll be able to give better feedback, but if it's mostly bugfixes and
couple of *new* functionality, but not breaking the old behaviour, I
would maybe support the idea of having it in F17 as well.
With regards,
Martin
4:24 p.m.
gxine is/was that multimedia player? I think Puppy Linux used/uses it a lot.
I remember it has many configuration options (old style app) and always
worked well for me (videos from the browser/on-line).
But if it's that one then it isn't in the Xfce spin, which uses
Parole(video)/Pragha(audio).
I've built newer exo/thunar and have good impressions. For me it solved
'Thunar --daemon' from xfce4-session crashing.
I don't have networks etc. so it would be good people that have those
testing. I think several related bugs have been fixed.
UI-wise it just changed the side-pane to something inspired on nautilus.
Looks fine.
12:25 p.m.
On Mon, 3 Dec 2012 22:27:10 +0100
Martin Sourada <martin.sourada(a)gmail.com> wrote:
Hi,
On Mon, 03 Dec 2012 17:54:32 +0100
Christoph Wickert wrote:
...snip...
> Here is my suggestion:
> F17: Probably not.
*cough-cough* What about the xfce-4.10 repo?
I will probibly update that...
> F18: Lets deliver it as a 0-day update, to minimize the change
of
> the user experience. Otherwise we'll have to support Thunar 1.4
> till the F18 EOL and by that time, 1.8 will probably be out already.
Seems sane to me to do the 0-day update, definitely better than having
to support 1.4 till F18 EOL ourselves.
I don't like the idea. If we are going to push it in, we should do so
now before final freeze. Waiting and making it a 0 day means we get
less testing before final to fix anything.
I'm going to test it myself to see how big the changes in UI are,
then
I'll be able to give better feedback, but if it's mostly bugfixes and
couple of *new* functionality, but not breaking the old behaviour, I
would maybe support the idea of having it in F17 as well.
I've not tested it either yet, but I don't think f17 will be viable.
It's still on 4.8 and exo is depended on by a lot of things.
I do think we should push to f18 asap tho. ;)
kevin
4:16 a.m.
Am Montag, den 03.12.2012, 22:27 +0100 schrieb Martin Sourada:
Hi,
On Mon, 03 Dec 2012 17:54:32 +0100
Christoph Wickert wrote:
> Am Montag, den 03.12.2012, 10:37 -0200 schrieb Sergio:
> > Please, take my boldness lightly but I'm already expecting
> > http://mail.xfce.org/pipermail/xfce/2012-December/031768.html
> > http://mail.xfce.org/pipermail/xfce/2012-December/031769.html
> > appear in updates-testing ;-)
>
> Two remarks:
> 1. Please don't *expect* something unless you do it yourself.
> 2. I am not the new version will hit F17. It's a change of the
> user experience that violates our update policy [1] and it missed
> beta freeze, so I am not even sure we could bring it to F18.
Yeah, and still firfox gets updated mid release whenever new major
release is out (I wonder when it last broke gxine build, not to
mention it actually working :()...
I agree the Firefox development model and versioning scheme is broken,
but that doesn't mean that we have to break other stuff, too. ;)
> Here is my suggestion:
> F17: Probably not.
*cough-cough* What about the xfce-4.10 repo?
As it isn't an official repo anyway, the update policy does not apply.
> F18: Lets deliver it as a 0-day update, to minimize the change
of the
> user experience. Otherwise we'll have to support Thunar 1.4 till the
> F18 EOL and by that time, 1.8 will probably be out already.
Seems sane to me to do the 0-day update, definitely better than having
to support 1.4 till F18 EOL ourselves.
Right. Note that this always is a problem, the Xfce and Fedora
development cycles don't go together well and we either have to ship a
development version at the beginning or support an outdated one
later. :( 1.6 should buy us some time here.
Kind regards,
Christoph
4:17 a.m.
Am Dienstag, den 04.12.2012, 11:25 -0700 schrieb Kevin Fenzi:
On Mon, 3 Dec 2012 22:27:10 +0100
Martin Sourada <martin.sourada(a)gmail.com> wrote:
> Seems sane to me to do the 0-day update, definitely better than having
> to support 1.4 till F18 EOL ourselves.
I don't like the idea. If we are going to push it in, we should do so
now before final freeze. Waiting and making it a 0 day means we get
less testing before final to fix anything.
Fine with me, if you can convince Adam. :)
Kind regards,
Christoph
1:59 a.m.
On Tue, Dec 4, 2012 at 7:25 PM, Kevin Fenzi <kevin(a)scrye.com> wrote:
On Mon, 3 Dec 2012 22:27:10 +0100
Martin Sourada <martin.sourada(a)gmail.com> wrote:
> Hi,
>
> On Mon, 03 Dec 2012 17:54:32 +0100
> Christoph Wickert wrote:
...snip...
> > Here is my suggestion:
> > F17: Probably not.
> *cough-cough* What about the xfce-4.10 repo?
I will probibly update that...
> > F18: Lets deliver it as a 0-day update, to minimize the change of
> > the user experience. Otherwise we'll have to support Thunar 1.4
> > till the F18 EOL and by that time, 1.8 will probably be out already.
> Seems sane to me to do the 0-day update, definitely better than having
> to support 1.4 till F18 EOL ourselves.
I don't like the idea. If we are going to push it in, we should do so
now before final freeze. Waiting and making it a 0 day means we get
less testing before final to fix anything.
> I'm going to test it myself to see how big the changes in UI are, then
> I'll be able to give better feedback, but if it's mostly bugfixes and
> couple of *new* functionality, but not breaking the old behaviour, I
> would maybe support the idea of having it in F17 as well.
I've not tested it either yet, but I don't think f17 will be viable.
It's still on 4.8 and exo is depended on by a lot of things.
I do think we should push to f18 asap tho. ;)
kevin
Thanks Kevin, just applied the two updates this morning! Finally there are
tabs in Thunar, weird ;-)
_______________________________________________
xfce mailing list
xfce(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/xfce
4174
days inactive
4177
days old
10 comments
6 participants
participants (6)
-
Christoph Wickert -
Johannes Lips -
Kevin Fenzi -
Martin Sourada -
Sergio Cipolla -
Tim Lauridsen