I have raised https://issues.apache.org/bloodhound/ticket/98 for this
task but we can continue the discussion of the timing here.
My suggestion that things could be odd for a bit would probably be
remedied by the completion of #93. As long as it doesn't take too long
and nothing is broken at that point.
It may also be worth considering whether that is good enough to call a
candidate release. I don't think we need to worry about tagging until
the release candidate is reached.
Cheers,
Gary
On 06/13/2012 12:18 AM, Olemis Lang wrote:
IMO , it's better to wait for committing changes in #93 which are mainly :
- continuous milestone view
- continuous dashboard
- enhanced product pages
nonetheless , may that's not as relevant as I might think myself
considering how often it will be updated . I suggest to tag versions
installed on the site .
PS: continuous = no button toolbar
On 6/12/12, Gary Martin<[email protected]> wrote:
I just noticed that I unintentionally only sent my reply directly to
Mark. Sorry about that. Here is what should have been sent:
Hi Mark,
I have no objection. It might be a little odd to use for a short period
while we sort the dashboard views out but it should remain functional.
Cheers,
Gary
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?
--
Mark Poole
WANdisco, Inc.
UK : +44 (0)114 303 0470
USA : +1 925 396 1104
http://www.wandisco.com
