Another bugfix release for xfce4-notifyd: 0.3.3 is out!

notifydWhile I had planned to make the next release about features, I ended up fixing a few issues and doing a bugfix release instead. So 0.3.3 is about getting things right.

Test-driven development

Generally speaking Xfce has very few unit tests – or tests at all – but since Jerome had laid a foundation for notification tests in xfce4-notifyd I decided to extend that to testing the icons in notifications. What inspired me to do so was that I noticed that notifyd was not in line with the fd.o notifications specification in two aspects:

  • it didn’t support the “image-path” hint and
  • the priorities of how to handle the icons were mixed up.

So my new “test-icons” test – which I wrote before(!) I implemented the fix for the priorities, even if I checked it into git only until later šŸ˜‰ – checks whether the server handles all icon-related properties, hints and features and also checks whether the priority is in accordance with the specification. I also started some documentation on what parts of the specification are implemented in xfce4-notifyd and which ones are not (prominent example which is not implemented: sound).

Other than that a thank-you goes to Olivier for contributing another build-fix. Finally I managed to get a few more bugs fixed, most notably a general theming issue (action buttons were sometimes mis-styled) and hiding notification buttons without label. Together with the translation updates I think this makes 0.3.3 a worthwhile release.

Final note: currently there are only 12 bugs open on the tracker, of which several are feature requests so things seem to be going quite well!

3 thoughts on “Another bugfix release for xfce4-notifyd: 0.3.3 is out!”

  1. Hey Simon

    I love XFCE and I would like to contribute to the project. I can’t code but I wouldn’t mind doing some testing. What can I do?

  2. Hi again!

    I tried doing as you said about this notification center thing I mentioned the other day, trying to post a bounty for it. I noticed someone else had already requested something similar, so I added a comment and tried to find the bug on Bountysource, but it doesn’t seem to be there. I haven’t done this before, so I’m sorry if I’m overlooking something obvious, but how can I post a bounty for this thing?

    Maybe I ought to create a new bug report?

Comments are closed.