Tuesday, May 30. 2006K3MI had a great time at the meeting, there’s nothing like the intensity of a hackathon, and actual face-to-face discussion to make you super productive. Many thanks to KDE NL for organising the event, especially since we offered such amazing disorganisation in return! For fun, here’s me, markey and muesli (left-to-right) in Amsterdam, and then at aKademy 2 years ago in Stutgart.
I picked on us three as there was the comparison shot. Overtime though we’ve been visited by more and more people, some submitted a patch or two then joined development more actively. Getting involved really is that easy. Send a patch, come to IRC, prove you cope with the sometimes obscure mxcl/oggb4mp3/sebr sense of humor and you’ll soon be being asked for your opinion on stuff. Sebr mentioned that we have an excellent development team quite a few times at the meet, and it’s true. And may it long continue because we work well as a group and have each our own unique talents that when combined, keep the quality high. That’s not to say we can’t improve, and we discussed among other things, what should be done to make code quality higher, while not lessening release rate, and how to keep exploring new features, without making amaroK unwelcoming to new (and old) users. Tuesday, May 30. 2006K3MI had a great time at the meeting, there’s nothing like the intensity of a hackathon, and actual face-to-face discussion to make you super productive. Many thanks to KDE NL for organising the event, especially since we offered such amazing disorganisation in return! For fun, here’s me, markey and muesli (left-to-right) in Amsterdam, and then at aKademy 2 years ago in Stutgart.
I picked on us three as there was the comparison shot. Overtime though we’ve been visited by more and more people, some submitted a patch or two then joined development more actively. Getting involved really is that easy. Send a patch, come to IRC, prove you cope with the sometimes obscure mxcl/oggb4mp3/sebr sense of humor and you’ll soon be being asked for your opinion on stuff. Sebr mentioned that we have an excellent development team quite a few times at the meet, and it’s true. And may it long continue because we work well as a group and have each our own unique talents that when combined, keep the quality high. That’s not to say we can’t improve, and we discussed among other things, what should be done to make code quality higher, while not lessening release rate, and how to keep exploring new features, without making amaroK unwelcoming to new (and old) users. Tuesday, May 30. 2006Genesis - 1.4.1 beta1As I was busy reading the da vinci code, which I had to write an disquisition about, I recently got notified that there will be a beta release of amaroK 1.4.1, reason -> K4M3 (K3M). A view into my mailbox showed me about 100 unread mails in the commits folder...usually the amount doesn't get > 45
 So, on Sunday+2weeks (06-06-18) we will probably pull out amaroK 1.4.1 beta1 - advanced amaroK users might know that we don't do betas for x.x.y releases, reason for this beta are enormous changes in the GUI as well as the core. Those are mostly results of K4M3 (kde 4 mutlimedia meeting) which had lead to really great improvements and ideas. We plan 1.4.1 for 2 weeks after the beta (if there are no big problems) and probably apply a string freeze 1 week before release. As of now trunk includes:
I'm still trying to sort out the bugs in the amaroK nightly script, which moved together with my server from SUSE to Kubuntu (woooohoooo!). Not only that this is the first somewhat, trying to be professional, work in Ruby (using 4 times an external app - on 200 lines!) also getting the debian dir to work properly with SVN snapshots is really nifty stuff ... I really hope to get it done within the next few weeks. Maybe before 1.4.1 final |
Amarok LinksCalendarQuicksearchCategoriesSyndicate This BlogBlog AdministrationWe Listen To... Powered by
|
