linux-kernel - Tracking regressions for next release(s)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAG9S4UjTtm_Zx89udbB=Qew7vToWkE_GHc_f78Q-kbOuqh4NRg@mail.gmail.com>
Date:	Fri, 23 Mar 2012 07:01:19 +0100
From:	Maciej Rutecki <maciej.rutecki@...il.com>
To:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	"Rafael J. Wysocki" <rjw@...k.pl>, florian@...kler.org
Subject: Tracking regressions for next release(s)

Hi

For a long time (dealing with colleagues) we tracking regressions in
stable RC versions of the kernel. Because 3.3 is out, and it is time
thinking about tracking regressions for
next release. I believe that we need to do some summary and decide on
further action.

I am interested in the opinion of the developers, testers, and
everyone involved in the development of the kernel, if they thing that
tracking regressions and monitoring the quality makes sense,
especially since I met several times (put it mildly) dislike of such
work and the bugs are repaired relatively slowly. Perhaps someone has
comments or proposals for change (in the way of work or me).

I care about the opinion, because without the acceptance of the
community work does not make sense. I also do not insist, because I'll
have more time for other tasks such as testing.

Regards
-- 
Maciej Rutecki
http://www.mrutecki.pl
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/