<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>I'm all for it. My only concern is that it is pretty soon--we basically have two months and a half.</div><div><br></div><div>If we do stick to august first, i propose we compose a list of showstopper things that we need to cover, and then we go through that list and tick off what we can. And we make sure not to release until all showstoppers are taken care of. I feel that some organization would be good for us (the whole code-what-you-want-when-you-want model works great during long dev periods, but sometimes we gotta take care of the boring stuff too)..</div><div><br></div><div>thoughts?</div><div><br></div><div>leo</div><div><br></div><br><div><div>On Jun 12, 2008, at 8:21 AM, Gregory Meyer wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">Awesome idea, although it is closer than you'd think. It makes a lot of sense because as Mark said, ubuntu is a big distro, and it makes sense for that reason alone, we'll probably see all the other distros fall in behind in switching the default KDE desktop from 3.5 to 4.1 later this year, so it would make sense to have a stable, if not totally feature complete amarok2 for everybody.<br> <br><br><div class="gmail_quote">On Thu, Jun 12, 2008 at 4:57 AM, Maximilian Kossick <<a href="mailto:maximilian.kossick@googlemail.com">maximilian.kossick@googlemail.com</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> In my opinion there are two (mabye three) blockers left that we need<br> for 2.0: rudimentary media device support (actually: ipod support.<br> Although generic media device support would be nice too),<br> smart/dynamic playlists (a core feature of Amarok 1. afaik even winamp<br> has them these days), and maybe podcasts. everything else is not a<br> blocker for A2.0 in my opinion.<br> <br> The proposed schedule is doable, but every coder but the soc students<br> would have to concentrate on these few areas. I might even be able to<br> help if I can get A2 working on stupid osx...<br> <br> Max<br> <div><div></div><div class="Wj3C7c"><br> On Thu, Jun 12, 2008 at 9:35 AM, Nikolaj Hald Nielsen<br> <<a href="mailto:nhnfreespirit@gmail.com">nhnfreespirit@gmail.com</a>> wrote:<br> > I think this is a good idea and very doable if we start focusing<br> > heavily on getting stuff ready.<br> > Also, it will allow us to use the hackathon at Akademy ( where there<br> > will be a ton of Amarokers ) to add the final polish!<br> ><br> > - Nikolaj<br> ><br> ><br> > On Thu, Jun 12, 2008 at 9:29 AM, Mark Kretschmann <<a href="mailto:kretschmann@kde.org">kretschmann@kde.org</a>> wrote:<br> >> Hi all,<br> >><br> >> on IRC some of us have been discussing a possible deadline for the 2.0<br> >> release. The initial spark that started the discussion was the<br> >> announcement of the Kubuntu "next" release schedule. In short: We<br> >> would like Amarok 2 to become the default music player in the next<br> >> Kubuntu release.<br> >><br> >> Kubuntu "Intrepid Ibex" is scheduled for release in October 2008, with<br> >> a deadline for applications sometime in August. I'm fairly sure they<br> >> would accept an Amarok 2.0 on September 01, *if* Amarok turns out to<br> >> be stable at that point.<br> >><br> >> This release of Kubuntu will be completely centered around KDE 4.1. If<br> >> Amarok 2 will not be ready for the release, then probably Amarok 1<br> >> will be chosen as the default music player. As you've probably<br> >> noticed, KDE 3 applications are starting to look really outdated in a<br> >> KDE 4 environment, so this would be a shame.<br> >><br> >> Q: Why is this post so focused on Kubuntu?<br> >> A: It just so happens that the Kubuntu release schedule is fairly<br> >> compatible with our Amarok 2 progress and our own tentative release<br> >> plans. So I think it makes a good aim, even if we should miss the<br> >> deadline. Also, (K)ubuntu is of course a very popular distro, and it<br> >> is of special importance to the Amarok project. I do not mean to<br> >> downplay the importance of the other existing distros.<br> >><br> >> Q: What happens if a feature (e.g. from SoC students) is not ready?<br> >> A: No big deal. It will simply be pushed into Amarok 2.1.<br> >><br> >><br> >> Tentative release schedule for Amarok 2:<br> >><br> >> 1) 2.0 Alpha this month<br> >> 2) 2.0 Beta1 and Beta2 @ July / August<br> >> 3) 2.0 Final @ September 01<br> >><br> >><br> >> Thank you for reading, and please let me know your opinions :)<br> >><br> >> --<br> >> Mark Kretschmann<br> >> Amarok Developer<br> >> <a href="http://www.kde.org" target="_blank">www.kde.org</a> - <a href="http://amarok.kde.org" target="_blank">amarok.kde.org</a><br> >> _______________________________________________<br> >> Amarok-devel mailing list<br> >> <a href="mailto:Amarok-devel@kde.org">Amarok-devel@kde.org</a><br> >> <a href="https://mail.kde.org/mailman/listinfo/amarok-devel" target="_blank">https://mail.kde.org/mailman/listinfo/amarok-devel</a><br> >><br> > _______________________________________________<br> > Amarok-devel mailing list<br> > <a href="mailto:Amarok-devel@kde.org">Amarok-devel@kde.org</a><br> > <a href="https://mail.kde.org/mailman/listinfo/amarok-devel" target="_blank">https://mail.kde.org/mailman/listinfo/amarok-devel</a><br> ><br> _______________________________________________<br> Amarok-devel mailing list<br> <a href="mailto:Amarok-devel@kde.org">Amarok-devel@kde.org</a><br> <a href="https://mail.kde.org/mailman/listinfo/amarok-devel" target="_blank">https://mail.kde.org/mailman/listinfo/amarok-devel</a><br> </div></div></blockquote></div><br> _______________________________________________<br>Amarok-devel mailing list<br><a href="mailto:Amarok-devel@kde.org">Amarok-devel@kde.org</a><br>https://mail.kde.org/mailman/listinfo/amarok-devel<br></blockquote></div><br><div apple-content-edited="true"> <span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; 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; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; 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: 0px; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; 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: 0px; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>Leo Franchi<span class="Apple-tab-span" style="white-space: pre; "> </span>(650) 704 3680</div><div>Tufts University 2010 </div><div><br></div><div><a href="mailto:lfranchi@kde.org">lfranchi@kde.org</a></div><div><a href="mailto:leonardo.franchi@tufts.edu">leonardo.franchi@tufts.edu</a></div></div></div></div></div></div></span></div></span></div></span> </div><br></body></html>