[yocto-ab] Fwd: [yocto] ** bug squashing weekend - Jan 17 to 20, 2014

[Philip Balister]

We are going to start having regular bug squashing activities to try and
get more people working on bugs reported to the Yocto Project bugzilla.
This should help improve overall quality and make it easier for the
project to make releases on schedule.

We'd like to try and get as many people helping with this effort as
possible over the four day period. Please circulate this information
internally to your organizations and encourage people to help with the
effort.

In the future, we'll try and give more notice. This event is scheduled
on short notice due to various upcoming events that created scheduling
conflicts. We also plan to review the activity levels over the weekday
versus weekend periods and make adjustments in the future.

Thanks,

Philip


-------- Original Message --------
Subject: [yocto] ** bug squashing weekend - Jan 17 to 20, 2014
Date: Tue, 14 Jan 2014 17:24:44 -0500
From: Trevor Woerner <trevor.woerner at linaro.org>
To: openembedded-core <openembedded-core at lists.openembedded.org>,
openembedded-devel at lists.openembedded.org, yocto at yoctoproject.org

Hello all OE/Yocto enthusiasts!

https://bugzilla.yoctoproject.org/

It has been noted that the number of unresolved issues in our bugzilla
has been rising which, if left unchecked, will lead to an
ever-increasing bug count. In an effort to raise awareness of the number
of unresolved bugs and work to reduce them, we'd like to plan a "bug
squashing weekend" for this upcoming Friday to Monday (January 17th to
20th, 2014).

If you work with OE/Yocto during the week then you'll have two days to
look at issues, or if you have more time on weekends you'll also have
two potential days for this activity.

It would be nice if anyone involved in OE/Yocto could take some time
between now and Monday to have a look at the bugzilla database and
consider contributing towards reducing the number of opened issues.
Obviously if you're a maintainer or some sort of a developer there are,
most likely, obvious issues you could consider addressing. But there are
also lots of issues an OE/Yocto "user" could investigate as well -- for
example there are documentation issues, there are several issues in the
"NEEDINFO" state, and sometimes just being able to reproduce a bug (or
not) and confirm (or not) that an issue can be demonstrated on more than
one host can be valuable information for the person who does eventually
get assigned to solve the problem.

Please take the opportunity to have a look at the opened issues in the
bugzilla database. If you don't have an account, please consider signing
up. Play with the "Search" capability (you'll probably want to try an
advanced search,
https://bugzilla.yoctoproject.org/query.cgi?format=advanced) and see if
there are issues to which you might want to contribute.

In an effort to keep multiple people from working on the same issues
during this sprint, please let the community know on which bugs you'd
like to work. You could reply to this email (keeping all the mailing
lists CC'ed), and/or you could re-assign a bug to yourself.

There are usually plenty of friendly, knowledgeable people around who
can help. You can use the mailing lists, IRC channels, or bugzilla
itself to communicate.
https://www.yoctoproject.org/tools-resources/community

Thanks for your participation! :-)

https://bugzilla.yoctoproject.org/
_______________________________________________
yocto mailing list
yocto at yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto