Mailing-List: contact bloodhound-commits-help@incubator.apache.org;
 run by ezmlm
Precedence: bulk
Reply-To: bloodhound-dev@incubator.apache.org
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "Apache Bloodhound" <bloodhound-dev@incubator.apache.org>
Cc: bloodhound-commits@incubator.apache.org
Auto-Submitted: auto-generated
Date: Wed, 13 Jun 2012 13:51:26 -0000
Reply-To: bloodhound-dev@incubator.apache.org
Subject: [Apache Bloodhound] #98: upgrade issues.apache.org/bloodhound to
 bloodhound
Message-ID: <052.c4975e87a3da225b6a4cc4e9dea3bdbd@incubator.apache.org>

#98: upgrade issues.apache.org/bloodhound to bloodhound
-----------------------+--------------------
 Reporter:  gjm        |      Owner:  nobody
     Type:  task       |     Status:  new
 Priority:  major      |  Milestone:
Component:  siteadmin  |    Version:
 Keywords:             |
-----------------------+--------------------
 From the bloodhound-dev mailing list:

 On 06/06/2012 04:57 AM, Mark Poole wrote:
 > Hi Guys,
 > I think eating our own dog food is important
 (http://en.wikipedia.org/wiki/Eating_your_own_dog_food).
 > I have been using the current development version of bloodhound on a
 deployment of around 8 people with 1500+ tickets for a few weeks now and
 things seem to be going well.
 > Would anyone mind if I upgrade the instance on bloodhound-vm to the
 current development build?

 Discussions continue in the bloodhound-dev mailing list regarding the
 timing of this work.

-- 
Ticket URL: <https://issues.apache.org/bloodhound/ticket/98>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker