GIMP 2.4.5

[echoes]

Binary package hint: gimp

GIMP 2.4.5 was released today, please update the package. (I know there may be issues due to FF/merging from Debian).

- fixed a regression introduced by the brush cursor optimization (bug #514309)
- fixed bug in transform tool preview (bug #340965)
- fixed PSD export of images with layer masks
- fixed base64 encoding routine of the Mail plug-in
- use the correct background color when creating a new image (bug #514082)
- explicitly link libgimpthumb with GLib (bug #515566)
- improved selection of the font sample string (bug #514021)
- unified handling of "Enter" and "Space" keysyms (bug #516544)
- fixed bug in the Glossy script when used with a pattern (bug #517285)
- correctly record dimensions in Exif data when saving as JPEG (bug #517077)
- fixed sensitivity of plug-in menu items (bug #517683)
- fixed potential crashes in Wind, Warp, Small Tiles and Apply Canvas plug-ins (bug #516369)
- added default keyboard shortcut for "Paste As New Image" (Ctrl-Shift-V)
- added default keyboard shortcut for "Copy Visible" (Ctrl-Shift-C)
- fixed missing preview update in Curves tool (bug #518012)
- fixed a bug in the Frosty Logo script (bug #472316)
- fixed backward transformations using the PDB (bug #518910)
- translation fixes and updates (de, eu, eo, fr, he, hu, it, ja, ko)

Contributors:

   Sven Neumann, Michael Natterer, Bill Skaggs, Kevin Cozens,
   Ulf-D. Ehlert, Giuliano Pochini, LightningIsMyName

Source:
http://gimp.org/downloads/#mirrors

[Caroline Ford (secretlondon)]

We are after feature freeze so this won't make hardy unless the feature freeze exception process is followed.

https://wiki.ubuntu.com/FreezeExceptionProcess

[Fred (eldmannen+launchpad)]

This is not a bug...

Also, they should add 16-bit color per channel to GIMP so it doesn't suck.

[Andrea Corbellini (andrea.corbellini)]

@Fred: all feature requests are wishlist bugs and please keep in mind the Ubuntu Code Of Conduct <http://www.ubuntu.com/community/conduct/>.

[echoes (echoes-deactivatedaccount)]

@ Caroline Ford
i already covered the FF in the description.

[Sebastien Bacher (seb128)]

There is no need to open bugs about new versions as soon any software roll a new tarball, you can work on the update and ask an exception though

[Murat Gunes (mgunes)]

echoes, but you didn't present all the data required. Read the page Caroline has pointed to.

[echoes (echoes-deactivatedaccount)]

@ Murat Güneş
i made this bug like i do all bugs. i mentioned the feature freeze so ppl would understand that this is a bug for future reference, not a FFe request. otherwise i would have put FFe in the tag. as i said, i made it for future reference, but if someone wants it included then they can voice their opinion.
this happened with a recent bug i filed (bug #197086). it was for future reference, not a FFe request, but someone else suggested it should get a FFe.

that being said/clarified, is it recommended procedure to not file bugs after a FF has gone into effect? the reason i ask is cuz the link provided about the FFe Process does not say anything in regards to the question i just asked.

[Murat Gunes (mgunes)]

> is it recommended procedure to not file bugs after a FF has gone into effect?

The recommended practice is to file a bug if you genuinely think the new release introduces features and/or fixes that should go into the current development branch, and won't do the work involved in the update yourself.

> the reason i ask is cuz the link provided about the FFe Process does not say anything in regards to the question i just asked.

You can't make a FFe request without filing a bug. This is stated under "General Instructions" on the page.