Just a short reminder that we are having our BugDays for Kmail starting tomorrow.
Please join starting from 10:00 UTC+2 (8:00 UTC) in #kde-bugs and #kde-testing on irc.freenode.net. Since there will be a big server move on that day we will not be able to access the KDE wikis and the forum for most of the European daylight period, so I created a public Etherpad you can find here: http://notes.kde.org/BugDayKmail Regards, Myriam On Wed, Aug 8, 2012 at 10:21 PM, Myriam Schweingruber <[email protected]> wrote: > Hi everyone, > > We are organizing a BugDay on 2 consecutive weekends to find the > kmail1 bugs reproducible in kmail2, so we can close the kmail1 > remaining bugs as unmaintained. > > You can find all the necessary information in my bog: > http://blogs.fsfe.org/myriam/2012/08/08/triagers-and-testers-needed/ > but here is a summary: > > What needs to be done? > > * We need to get rid of open duplicate reports. > * We will check if a bug is reproducible in Kmail 2 and reassign it there. > * We will close the Kmail1-only reports as unmaintained. > * We also need to clean up and remove duplicates form the Kmail2 bugs list. > > To make sure we can work reasonably well, this is the setup you should > have to help with the testing: > > * KDE SC 4.8.4 with Kmail 4.8.4 at least, but 4.9 would be better and > if you can run from Git it would be even more helpful. > * Either a POP3 or an IMAP setup, to make sure we can test both extensively. > > I will be around most of the time (in my UTC+2 timezone at least) and > will try to give a hand in #kde-bugs on irc.freenode.net > > So let’s meet on Saturday, August 18th on #kde-bugs and get this > sorted as much as possible. > > Of course, you can start earlier: you will find two saved searches in > http://bugs.kde.org called “Kmail1 open bugs” and “Kmail2 open bugs”. > Just add these to your footer, so you can easily access the list > whenever you feel a triaging itch. > (if you can't see saved searches then you do not yet have enough > rights in b.k.o, please talk to me about that so we can fix that). > > If this is your first triaging experience, don’t be shy, just ping me > in #kde-bugs – type: “Mamarok: ping” – and I will try to give you the > necessary help ASAP > > And finally: if you want to be kept updated about the Bugsprints we > organize, you can subscribe to this Calendar: > https://www.google.com/calendar/ical/8q4v2jv05dusqo03lq53mtdqqg%40group.calendar.google.com/public/basic.ics > > > See you on Saturday! > > Regards, Myriam > > PS. A good read for triagers 2be: > http://techbase.kde.org/Contribute/Bugsquad/Guide_To_BugTriaging > > -- > Proud member of the Amarok and KDE Community > Protect your freedom and join the Fellowship of FSFE: > http://www.fsfe.org > Please don't send me proprietary file formats, > use ISO standard ODF instead (ISO/IEC 26300) -- Proud member of the Amarok and KDE Community Protect your freedom and join the Fellowship of FSFE: http://www.fsfe.org Please don't send me proprietary file formats, use ISO standard ODF instead (ISO/IEC 26300) _______________________________________________ Kde-testing mailing list [email protected] https://mail.kde.org/mailman/listinfo/kde-testing
