Thanks for your job! I think it's really great to define what's really important to do before the release.
So guys let fix all of those ;) On Wed, Sep 26, 2012 at 7:08 PM, Thomas Müller <thomas.muel...@tmit.eu> wrote: > As stated many times already: we will address this on the dev meeting in > Berlin end of Oct. > > Nothing more to be said. > > Thx > > Tom > > PS: As I sometimes get missunderstood: this message is not intended to be > offensive. ;-) > > Torsten Grote <gr...@kolabsys.com> schrieb: > >>On Wednesday 26 September 2012 18:36:29 Arthur Schiwon wrote: >>> Frank asked me to get an overview about the remaining bugs. So I did and >>> updated the spreadsheet [1]. >> >>Wouldn't it be a good idea to eventually use a proper bug tracking software >>that has this functionality built in, especially since so many people seem >>to have problems with the current tracker? >> >>In the Kolab Community for example we use Bugzilla and it allows you to easily >>list the blocker bugs for the upcoming release of Kolab 3: >> >>https://issues.kolab.org/buglist.cgi?bug_severity=blocker&target_milestone=3.0-next >> >>Regards, >>Torsten >> >>-- >>Torsten Grote, Kolab Evangelist >> >>Kolab Systems AG, Zürich, Switzerland >> >>e: gr...@kolabsys.com >>t: +41 43 501 66 91 >>w: http://kolabsys.com >> >>pgp: 274D 4F97 Torsten Grote >> >>_______________________________________________ >>Owncloud mailing list >>Owncloud@kde.org >>https://mail.kde.org/mailman/listinfo/owncloud > _______________________________________________ > Owncloud mailing list > Owncloud@kde.org > https://mail.kde.org/mailman/listinfo/owncloud _______________________________________________ Owncloud mailing list Owncloud@kde.org https://mail.kde.org/mailman/listinfo/owncloud