We *really* need to fix more bugs! (Was: Bug squashing in December (Was: December))
I admit I didn't noticed the expected bump in a higher bug fixing
activity. But we *really* need this. I've personally set a one bug per
day policy for myself and on close to all days I squashed more than
this. The point is not that I want to demonstrate how busy I am but how
*easy* it partly is to squash a bug. I just fixed one in 2 minutes
(#884269 - well that was a really simple one caused by myself and it
would have been better if I would not point on this shame ;-) ) but I
think at least half of the bugs I squashed took about 15min. Yes, its
perfectly fine if you, yes *you* who are reading this mail, pick a low
hanging fruit. But the feeling after having squashed a bug is really
nice - trust me, I've been there. ;-)
Despite a fact that I managed to squash 3 yesterday we received 4 new
ones - so I really can not manage this alone.
Its not really that we have many bugs in total compared to the amount of
packages we are maintaining. However, we do not have a large group of
users and we should care for every single one. If a user feels ignored
after having reported an issue that's a good reason for a user to
question the decision to use Debian and to become active (by reporting
a bug). That has to be avoided.
So please, pretty please, everyone set at least a one bug per month
policy for your own - better a one bug per week. That would be 15min
per week if you takle a simple one. Compared to the time you safe since
Debian Med exists that's not so much IMHO.
Thanks a lot for joining our bug squashing party
On Wed, Dec 06, 2017 at 10:40:33AM +0100, Andreas Tille wrote:
> Hi Debian Med fans,
> may be the subject of the original mail was not catchy enough and people
> did not realised that we are doing a 24 day internet wide bug squashing
> party. Believers in different tradition than advent are welcome to join
> as well, for sure.
> I admit I have not realised a dramatic bump in bug fixing activity. It
> would be *really*, *really* nice if everybody who thinks that Debian Med
> is helpful for personal work and who wants to contribute tries to squash
> at least one bug in this time period, better one per week. We really
> need to get our bug count done and there are low hanging fruits on our
> list. You can also ask for help here if you have no idea how to squash
> a bug.
> Thanks for your contribution
> On Fri, Dec 01, 2017 at 08:39:56AM +0100, Andreas Tille wrote:
> > Hi everybody,
> > its really that simple to close a bug which I'm doing here without a line
> > of code closing my first bug in this mail after having checked that zstd
> > has hit backports and adding "firstname.lastname@example.org" to the list of
> > receivers of this mail.
> > Not all bugs are *that* simple to solve but **everybody** is kindly
> > invited to head for the simple ones right now.
> > On Thu, Nov 30, 2017 at 12:44:39PM +0100, Thorsten Alteholz wrote:
> > > Hi everybody,
> > >
> > > this time of the year has come again and in order to carry on a tradition
> > > (it is the seventh time this year), I want to remind everybody of our
> > > combined efforts to take care of some poor souls.
> > >
> > > The days are closing in, the year is drawing to an end and we should think
> > > of all those, that are not around with their own kind. Again, during the
> > > last few months, lots of volunteers all around the world tracked down those
> > > poor souls and put their cases in the database. We should take care of those
> > > needy. This year, there are about 180 cases which are relevant to Debian
> > > Med (this time 21 are serious). So please feel pity for them and allow
> > > the transition of as many as possible poor souls to their final destination,
> > > the retirement community in the Archive. Maybe some of the "won't fix" can
> > > be resolved as well.
> > We should definitely try to fix the serious ones - even if they are mostly
> > not that simple.
> > > Furthermore I would like to mention another page with lots of information
> > > about Debian Med packages. Besides the list of RC bugs you can also see
> > > packages that can not be built on a Debian architecture, packages that are
> > > not allowed to migrate from unstable to testing (and thus won't be included
> > > in the next release) and packages with a new upstream version. I think those
> > > packages need some care as well.
> > Definitely.
> > > As soon as I get the notice of a closed case I will record that in our
> > > Advent calendar. In contrast to normal calendars, let us fill this
> > > special one with lot s of good deeds. Maybe we can hide at least one number
> > > of a closed case behind every door.
> > >
> > > I would like to mention #225651  here, as this seems to be the oldest one
> > > that needs some help (at least a proper closing).
> > Pinging Aaron explicitly to refresh his statement given several years ago.
> > > Have fun,
> > > Thorsten
> > Thanks for the fun and all your work
> > Andreas.
> > > http://bugs.debian.org/cgi-bin/pkgreport.cgi?which=maint&data=debian-med-packaging%40lists.alioth.debian.org&archive=no&raw=yes&bug-rev=yes&pend-exc=fixed&pend-exc=done
> > > http://bugs.debian.org/cgi-bin/pkgreport.cgi?which=maint&data=debian-med-packaging%40lists.alioth.debian.org&archive=no&pend-exc=done&sev-inc=critical&sev-inc=grave&sev-inc=serious
> > > http://email@example.com
> > > http://debian-med.alteholz.de/advent-2017
> > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=225651
> > >
> > --
> > http://fam-tille.de