On 17/02/15 14:28, John Chambers wrote:
Ok I think we have a plan. Now I just need to figure out how to implement
it ;)
The only thing is I think I am going to have to involve INFRA because I
think the only way into our VM is via https://issues.apache.org/bloodhound
and I don't think making any config changes to the Apache2 config on the vm
will allow external access via another url i.e
https://issues.apache.org/bhound.
I am going to try and test this by installing a new instance of bloodhound
0.8.0 on the VM and try and access it via the above url. If this is not
possible I will raise this with INFRA. They may also be the ones who can
setup the redirect from https://issues.apache.org/bloodhound to
https://issues.apache.org/bhound/product/BLOODHOUND
I will keep you informed.
Cheers
John
Yes, it is probably wise to talk with INFRA about this to figure out
what they need to do. With our assumption that they will eventually take
control of the running, they might wish to assert their preference
instead. I don't think we need to be overly attached to a particular path.
Incidentally, I think I specified the wrong redirect in my last message
as we use products rather than product so that redirect should be:
https://issues.apache.org/bloodhound =>
https://issues.apache.org/bhound/products/BLOODHOUND
So, has anyone got any problems with this part of the plan? Is there
anything that anyone thinks will come back to haunt us?
Cheers,
Gary
