Bug 1319388 - xfce4-power-manager 1.6.0 released
Summary: xfce4-power-manager 1.6.0 released
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: xfce4-power-manager
Version: 22
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Mukundan Ragavan
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-19 10:41 UTC by Ali Akcaagac
Modified: 2016-03-26 12:39 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-03-26 12:39:17 UTC
Type: Bug


Attachments (Terms of Use)

Description Ali Akcaagac 2016-03-19 10:41:40 UTC
A couple of days ago xfce4-power-manager 1.6.0 got released which covers all the bugfixes that fedora applied as separate patches to their own git. This release even covers a few more fixes and language improvements. Would be nice to see that one as package.

Thanks!

Comment 1 Mukundan Ragavan 2016-03-19 11:55:02 UTC
Indeed. 

I am heading out at the moment. But, I will push this today evening. Was there an announcement email about this? If there was, I have most certainly missed it ... :(

Comment 2 Kevin Fenzi 2016-03-19 19:00:02 UTC
There wasn't any announcement. ;( 

I thought they were going to get a few more fixes in, but I guess they are saving those for 1.6.1. ;(

Comment 3 Ali Akcaagac 2016-03-19 21:17:24 UTC
No announcement for Whisker Menu as well. A new version got released 3.5 months ago and I kept bugging the maintainer for an update.

https://bugzilla.redhat.com/show_bug.cgi?id=1294821

If you are at it, maybe updating this will benefit everyone else.

Comment 4 Mukundan Ragavan 2016-03-20 19:57:27 UTC
Build done. But, I am going to see if there is going to be an 1.6.1 update soon. I want to see if the "not shown in MATE" fix land in a new release (and hence no release announcement).


https://koji.fedoraproject.org/koji/buildinfo?buildID=746763


Note You need to log in before you can comment on or make changes to this bug.