Return-Path: X-Original-To: apmail-bloodhound-user-archive@www.apache.org Delivered-To: apmail-bloodhound-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id E7FBE1028E for ; Tue, 16 Dec 2014 18:07:40 +0000 (UTC) Received: (qmail 89826 invoked by uid 500); 16 Dec 2014 18:07:40 -0000 Delivered-To: apmail-bloodhound-user-archive@bloodhound.apache.org Received: (qmail 89799 invoked by uid 500); 16 Dec 2014 18:07:40 -0000 Mailing-List: contact user-help@bloodhound.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@bloodhound.apache.org Delivered-To: mailing list user@bloodhound.apache.org Received: (qmail 89789 invoked by uid 99); 16 Dec 2014 18:07:40 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 16 Dec 2014 18:07:40 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of michael.jinks@gmail.com designates 209.85.220.54 as permitted sender) Received: from [209.85.220.54] (HELO mail-pa0-f54.google.com) (209.85.220.54) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 16 Dec 2014 18:07:36 +0000 Received: by mail-pa0-f54.google.com with SMTP id fb1so14519239pad.41 for ; Tue, 16 Dec 2014 10:06:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=HrHi5H1RZCNhN2mY5/P2e5IlG1efw44Fdk0meRlSWCI=; b=uNmjY7HkCp3JfARqX9zlzpLFfa70B4x6aJN+jfI3YImjt7RSAbdw7q1QvqaZYAszCp vEbfXWXSmvO23DYXBshvc5sVNEavIqnCp1A0hoSKK1HXEf/3V+i+8zfhVa8RS5jLlMBy BsicGrD8KUAhLAV89oZGciOExV6qLADnakNmPrd9CHbwOsuxfoiJoyAe+qZ3CHu0+bW9 4YzqQhRSGEwiFwOyWd1stHTL2R8YI+Z0YQykFzwVLInuGlUzxfE6FnairZNIQTgL3GW8 NRjpjT1Qy/L5lSBp0RFVmU8muNsSEjgz62kmR1pVRphtw2TDiCTiSxKNmx4RzfNmVmFf E21A== MIME-Version: 1.0 X-Received: by 10.70.90.10 with SMTP id bs10mr50860642pdb.165.1418753190614; Tue, 16 Dec 2014 10:06:30 -0800 (PST) Received: by 10.66.78.104 with HTTP; Tue, 16 Dec 2014 10:06:30 -0800 (PST) In-Reply-To: <549067D3.6050603@millcomputing.com> References: <549067D3.6050603@millcomputing.com> Date: Tue, 16 Dec 2014 12:06:30 -0600 Message-ID: Subject: Re: Broken demo link From: Michael Jinks To: user@bloodhound.apache.org Content-Type: multipart/alternative; boundary=001a11c22310f35e9e050a593761 X-Virus-Checked: Checked by ClamAV on apache.org --001a11c22310f35e9e050a593761 Content-Type: text/plain; charset=UTF-8 More broadly... What's the QA landscape for this project? I sort of get the impression that this is one of those projects that works well for the people creating it, but doesn't get much in the way of formal review on its way to release. That's great if the releases are frequent and allow those of us at the endpoint to do our own dev/test/push cycle in the face of incremental changes each time we see a fresh version, but with infrequent releases showing major changes that's a tough pattern to maintain. Sorry to gripe. I like Bloodhound a lot and I'm pushing for its success. On Tue, Dec 16, 2014 at 11:11 AM, Arthur Kahlich wrote: > > I am sure you already know about this. > > I have a couple of older guys looking at bloodhound as part of an > evaluation of which issue tracker to go with. Naturally, both of them > within *seconds* of looking at the default local installed home page > without any prompting went to the bloodhound home page and hit the > broken demo link. It's a bad first impression, and if not fixed it > should be removed. I will certainly be removing *any* links to the > bloodhound home pages that contain the broken link from my installation. > These 2 guys were my friendly reviewers - some others will not be so > friendly, with a couple of them that may be downright hostile. > > -- > Arthur Kahlich > CTO - Hardware > Mill Computing, Inc. > Box 1531 > Palo Alto CA 94302-1531 > Phone: (408)480-3680 > -- > Faster, Cooler, Safer Computing. > -- > > --001a11c22310f35e9e050a593761 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
More broadly... What's the QA landscape for this proje= ct? I sort of get the impression that this is one of those projects that wo= rks well for the people creating it, but doesn't get much in the way of= formal review on its way to release. That's great if the releases are = frequent and allow those of us at the endpoint to do our own dev/test/push = cycle in the face of incremental changes each time we see a fresh version, = but with infrequent releases showing major changes that's a tough patte= rn to maintain.

Sorry to gripe. I like Bloodhound a lot = and I'm pushing for its success.



On Tue, Dec 16= , 2014 at 11:11 AM, Arthur Kahlich <art@millcomputing.com> wrote:
I am sure you already know about th= is.

I have a couple of older guys looking at bloodhound as part of an
evaluation of which issue tracker to go with. Naturally, both of them
within *seconds* of looking at the default local installed home page
without any prompting went to the bloodhound home page and hit the
broken demo link. It's a bad first impression, and if not fixed it
should be removed. I will certainly be removing *any* links to the
bloodhound home pages that contain the broken link from my installation. These 2 guys were my friendly reviewers - some others will not be so
friendly, with a couple of them that may be downright hostile.

--
Arthur Kahlich
CTO - Hardware
Mill Computing, Inc.
Box 1531
Palo Alto CA 94302-1531
Phone: (408)480-36= 80
--
Faster, Cooler, Safer Computing.
--

--001a11c22310f35e9e050a593761--