From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: X-Spam-Status: No, score=-2.9 required=3.0 tests=ALL_TRUSTED,AWL,BAYES_00, URIBL_BLOCKED shortcircuit=no autolearn=unavailable version=3.3.2 X-Original-To: unicorn-public@bogomips.org Received: from localhost (dcvr.yhbt.net [127.0.0.1]) by dcvr.yhbt.net (Postfix) with ESMTP id 56D1C1F80A; Tue, 10 Feb 2015 17:06:58 +0000 (UTC) Date: Tue, 10 Feb 2015 17:06:58 +0000 From: Eric Wong To: unicorn-public@bogomips.org Subject: [PATCH] ISSUES: add section for bugs in other projects Message-ID: <20150210170658.GA28272@dcvr.yhbt.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline List-Id: This is not anything new, just documenting what has been going on since the beginning. There's been a small number of generic networking (or mm) bugs in the kernel which affect unicorn, but are usually found and fixed with more popular, non-Ruby servers, first. Aside from generic performance problems, I don't think there's ever been a glibc bug which affected unicorn. --- ISSUES | 30 ++++++++++++++++++++++++++++++ 1 file changed, 30 insertions(+) diff --git a/ISSUES b/ISSUES index f66d14a..343cab4 100644 --- a/ISSUES +++ b/ISSUES @@ -18,6 +18,36 @@ instead and your issue will be handled discreetly. If you don't get a response within a few days, we may have forgotten about it so feel free to ask again. +== Bugs in related projects + +unicorn is sometimes affected by bugs in its dependencies. Bugs +triggered by unicorn in mainline Ruby, rack, GNU C library (glibc), +or the Linux kernel will be reported upstream and fixed. + +For bugs in Ruby itself, we may forward bugs to +https://bugs.ruby-lang.org/ and discuss+fix them on the ruby-core +list at mailto:ruby-core@ruby-lang.org +Subscription to post is required to ruby-core, unfortunately: +mailto:ruby-core-request@ruby-lang.org?subject=subscribe + +For uncommon bugs in Rack, we may forward bugs to +mailto:rack-devel@googlegroups.com and discuss there. +Subscription (without any web UI or Google account) is possible via: +mailto:rack-devel+subscribe@googlegroups.com +Note: not everyone can use the proprietary bug tracker used by Rack, +but their mailing list remains operational. + +Uncommon bugs we encounter in the Linux kernel should be Cc:-ed to the +Linux kernel mailing list (LKML) at mailto:linux-kernel@vger.kernel.org +and other kernel lists such as mailto:netdev@vger.kernel.org +(for networking issues). No subscription is necessary, and the our +mailing list follows the same conventions as LKML for interopability. + +Likewise for any rare glibc bugs we might encounter, we should Cc: +mailto:libc-alpha@sourceware.org +Keep in mind glibc upstream does use Bugzilla for tracking bugs: +https://sourceware.org/bugzilla/ + == Submitting Patches See the HACKING document (and additionally, the -- EW