There's an info about new version (1.3.8) of AmaroK on http://amarok.kde.org. An update is wanted :)
So let's put some things clear, like this was the first time: - developers who maintains packages usually are subscribed to lists, or watches RSS feeds, or KDE-Apps; - developers who maintains packages with _scheduled_ releases know when they are due; - in particular, amaroK developers inform the packages (included me) when _pre_ releases are available so that we can start preparing the packages (or the ebuilds); - in this particular case, I was in #amarok when the release was done; - I wrote on my blog (http://planet.gentoo.org/developers/flameeyes/2006/01/15/prepare_yourself_for_new_amarok_ebuilds) about the upcoming release and changes, and I put on my overlay (http://dev.gentoo.org/~flameeyes/bzr/overlay ) the RCs ebuild; - I never missed an amaroK release since I'm taking care of it of more than one day; - the release was done just a couple of hours ago; - it's not yet announced on kde-apps or kde-extra-gear mailing lists; - the bloody ebuild is already in the tree, I committed it about half an hour after tagging, so less than half an hour from the official release (time to download the tarball, build it, see that it runs, put it on toucan as there were problems with sf's mirrors, and commit) as you can see by the time of my commit ( http://cia.navi.cx/stats/author/flameeyes/.message/236e6d ) vs the one markey did to tag amarok 1.3.8 ( http://cia.navi.cx/stats/author/markey/.message/72a7b ) -count after that the tarball creation-; - yet another bug was filed for amaroK 1.3.8. That said, please next time don't report a bump unless it's older than one week and search before doing so.
