Version 0.12.11 released yesterday: * Fixed selection in the audio CD ripping window. * Fixed info block handling in WAVE audio file decoder: no more clicks at the end. * Introduced a hack which fixes the "Wav detected as Mpeg file" bug. * Fixed Auto multisession mode for DVD+RW and DVD-RW in restricted overwrite mode in case a previous session was imported. * Fixed a crash with HAL >= 0.5 when exiting K3b. * Allow copying of double layer DVDs with a size below 4.3 GB to single layer media. * Support for the ring buffer in growisofs 6.0. * Use .iso extension for images instead of .img * Properly remove the image file in case verification failed. * Ignore mounting state of a medium when showing its contents. * Fixed a bug in the iso options code which sometimes resulted in a failed verification. * Properly handle cue files withan image file name like image.bin.cue + image.bin * Write a proper Xing header when encoding VBR mp3 files.
Please don't file a bug for a new version unless we don't react within a week. We see the announcements as well.
That's a new policy then. Is this general or does it apply only to k3b?
(In reply to comment #2) > That's a new policy then. Is this general or does it apply only to k3b? > It's general...Sorry we don't have the ebuilds ready for the tree the day they come out :P
(In reply to comment #2) > That's a new policy then. Is this general or does it apply only to k3b? You might want to read this before asking more questions... :=) http://planet.gentoo.org/developers/flameeyes/2006/01/16/how_to_annoy_an_ebuild_developer
Well, I do see the problem. However, I also see bugzilla as a tool to track the addition of updated versions with, for example, confirmations that renaming the ebuild resulted in a working merge or that this and this dependency needs to be introduced. That's why I submit(ted) these bugs. (In this case here this probably was overkill as the update seems not to have any outside-code effects. But who can tell beforehand.. ;-) And no, I do not and did not expect updated versions in the tree the same day they come out, this bug was never meant to be harrassing in any way. And yes, I think for most changes in the portage tree there should be a corresponding bug to it. (However, bugzilla is not the place to discuss this, that's why I shut up now.. response over pm or irc (if I'm there) or join me on a beer in a pub :-) New version works for me, thanks.
