Well, #399 is effectively fixed - just not for the current release.
There are a few potential work-arounds for the issue on bh-demo2, including:
* override the offending code with some custom site js
* move the base path for the environment to
https://bh-demo2.apache.org/<somewhere>/
I don't particularly like either of these solutions as it is something
that will have to be reversed again. Still, possibly better to get it
done and at least the error is found.
Default data is a good idea - are we happy with taking tickets from
issues.apache.org/bloodhound to use for this for now?
Cheers,
Gary
On 19/02/13 11:34, Joachim Dreimann wrote:
Looks like a good starting point.
I reckon we need to fix #399 and add default content (tickets, milestones,
versions, products) before we can promote this further afield.
Without this we'd turn off the majority of users (those that browse and
those that want to create stuff) almost immediately in my opinion.
Cheers,
Joe
On 19 February 2013 11:04, Gary Martin <[email protected]> wrote:
Hi,
With a lot of help from Gavin, we now have the demos that we have been
discussed. These are at:
https://bh-demo1.apache.org/ (the nightly build of the latest code)
https://bh-demo2.apache.org/ (the latest release version of the code)
Both of these are scheduled to rebuilt once a day (I believe around 03:00
UTC) which results in both servers starting from a clean state with no
tickets or other changes. Please keep this in mind if you want to make use
of these servers to help report bugs.
The bh-demo2 suffers from the following bug which stops the Create Ticket
button working:
https://issues.apache.org/**bloodhound/ticket/399<https://issues.apache.org/bloodhound/ticket/399>
Cheers,
Gary
