On Sun, Feb 21, 2016 at 4:15 PM, Sam Ruby wrote:
> Over the next few days, I plan to work with the infrastructure staff to
> change things so that https://whimsy.apache.org/ is proxied to whimsy-vm2
> (currently only accessible via https://whimsy-test.apache.org/). This may
> cause applications t
On 23 February 2016 at 10:03, Sam Ruby wrote:
> On Tue, Feb 23, 2016 at 4:30 AM, sebb wrote:
>> This does not appear to have happened yet.
>
> Indeed, it has not. I've now opened a JIRA issue to track this
> https://issues.apache.org/jira/browse/INFRA-11311
>
>> Meanwhile, some of the fixes have
On Tue, Feb 23, 2016 at 4:30 AM, sebb wrote:
> This does not appear to have happened yet.
Indeed, it has not. I've now opened a JIRA issue to track this
https://issues.apache.org/jira/browse/INFRA-11311
> Meanwhile, some of the fixes have not been applied to the live copy -
> for example, I fix
This does not appear to have happened yet.
Meanwhile, some of the fixes have not been applied to the live copy -
for example, I fixed non-participants.cgi to remove a spurious / from
the committer links (which are currently broken for me on whimsy, but
not whimsy-test)
On 21 February 2016 at 21:1
Over the next few days, I plan to work with the infrastructure staff to
change things so that https://whimsy.apache.org/ is proxied to
whimsy-vm2 (currently only accessible via
https://whimsy-test.apache.org/). This may cause applications to break.
For a period of time (currently not defined)
