<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div>On Feb 12, 2009, at 4:52 PM, Jason Voegele wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: -webkit-monospace; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0; "><br>I'm not an Amarok or TagLib developer, but I'd say an important first step is<span class="Apple-converted-space"> </span><br>to get the ball rolling on TagLib 2.0. Previous messages in this thread have<span class="Apple-converted-space"> </span><br>indicated that many 2.0 enhancements are ready and are just waiting to be<span class="Apple-converted-space"> </span><br>committed. If that's true, I'd like to cast my vote for committing them now. <br></span></blockquote></div><br><div><br></div><div><div>I'm trying to finish up some stuff for our next release at work (unrelated to TagLib) and after that I'm planning on taking a few days to roll a TagLib 1.6 RC. I'd hoped to do that last week but our release got pushed back to this week, so I had to reshuffle things a bit. After that I'm fine with trunk being used for 2.0 development.</div><div><br></div><div>-Scott</div></div></body></html>