Xfce4 panel plugins - GTK3 port

[Mukundan Ragavan]

Hi folks,

As many of you may be aware, Xfce development team has been busy porting
the DE to GTK-3. Today, several plugins that were ported were released -
albeit as a development release.

The plugins that were released are below -

xfce4-

battery
datetime
diskperf
fsguard
mpc
netload
smartbookmark
systemload
wavelan

-plugin

Obviously, we would want to push these releases only to rawhide, in
which case, we have ~6 months before Fedora 25 happens which **may** be
sufficient time for any "issues" to be sorted out.

Should we update to these development releases or should be wait for the
next release? I have no preference either ways and I can build these if
that's what we want to do.

Mukundan.

[Johannes Lips]

On 06/06/16 03:13, Mukundan Ragavan wrote:
> Hi folks,
>
> As many of you may be aware, Xfce development team has been busy porting
> the DE to GTK-3. Today, several plugins that were ported were released -
> albeit as a development release.
>
> The plugins that were released are below -
>
> xfce4-
>
> battery
> datetime
> diskperf
> fsguard
> mpc
> netload
> smartbookmark
> systemload
> wavelan
>
> -plugin
>
> Obviously, we would want to push these releases only to rawhide, in
> which case, we have ~6 months before Fedora 25 happens which **may** be
> sufficient time for any "issues" to be sorted out.
>
> Should we update to these development releases or should be wait for the
> next release? I have no preference either ways and I can build these if
> that's what we want to do.

Hey Mukundan,

given the development speed of Xfce I would suggest, that we wait until 
the porting efforts are nearly complete and I doubt that will happen 
until f25. In my opinion it wouldn't look good if different parts of 
Xfce look and behave differently, or?

Thanks for your work,
Johannes
> Mukundan.
>
> xfce mailing list
> [e-mail]
> https://lists.fedoraproject.org/admin/lists/[e-mail]

[Dan Horák]

On Sun, 5 Jun 2016 21:13:28 -0400
Mukundan Ragavan  wrote:
> Hi folks,
>
> As many of you may be aware, Xfce development team has been busy
> porting the DE to GTK-3. Today, several plugins that were ported were
> released - albeit as a development release.
>
> The plugins that were released are below -
>
> xfce4-
>
> battery
> datetime
> diskperf
> fsguard
> mpc
> netload
> smartbookmark
> systemload
> wavelan
>
> -plugin
>
> Obviously, we would want to push these releases only to rawhide, in
> which case, we have ~6 months before Fedora 25 happens which **may**
> be sufficient time for any "issues" to be sorted out.
>
> Should we update to these development releases or should be wait for
> the next release? I have no preference either ways and I can build
> these if that's what we want to do.

can you setup a copr repo for them? This way they can get some testing
and still won't slip into F-25 if not fully released upstream.

Dan

[Kevin Fenzi]

On Mon, 6 Jun 2016 09:42:39 +0200
Dan Horák  wrote:
> On Sun, 5 Jun 2016 21:13:28 -0400
> Mukundan Ragavan  wrote:

...snip...
> > Should we update to these development releases or should be wait for
> > the next release? I have no preference either ways and I can build
> > these if that's what we want to do.
>
> can you setup a copr repo for them? This way they can get some testing
> and still won't slip into F-25 if not fully released upstream.

Yeah, I think a copr repo would be best.

I'd really not want to land them in rawhide and have the next release
take longer than f25 (although I suppose its not the end of the world
if some plugins are gtk3).

kevin

[Mukundan Ragavan]

On 06/06/2016 11:12 AM, Kevin Fenzi wrote:
> On Mon, 6 Jun 2016 09:42:39 +0200
> Dan Horák  wrote:
> > On Sun, 5 Jun 2016 21:13:28 -0400
> > Mukundan Ragavan  wrote:
>
> ...snip...
> > > Should we update to these development releases or should be wait for
> > > the next release? I have no preference either ways and I can build
> > > these if that's what we want to do.
> >
> > can you setup a copr repo for them? This way they can get some testing
> > and still won't slip into F-25 if not fully released upstream.
>
> Yeah, I think a copr repo would be best.
>
> I'd really not want to land them in rawhide and have the next release
> take longer than f25 (although I suppose its not the end of the world
> if some plugins are gtk3).
>
> kevin

OK folks, I will set up with a COPR for testing. That does sound like
the best course of action. I will post again when I have a working COPR.

Thanks for the responses.
Mukundan.