subversion-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bert Huijben" <>
Subject RE: ASF JIRA migration: Update our Tigris and Apache web sites
Date Fri, 02 Oct 2015 17:03:36 GMT

> -----Original Message-----
> From: Julian Foad []
> Sent: vrijdag 2 oktober 2015 17:27
> To: Ivan Zhakov <>; Mark Phippard
> <>
> Cc: dev <>
> Subject: Re: ASF JIRA migration: Update our Tigris and Apache web sites
> > I (Julian Foad) wrote:
> >> I've updated the ASF web site:
> The attached patch updates the 'issue-tracker.html' page on Tigris.
> However, my commit attempt fails although I have a login and password,
> presumably because the project is locked. Mark, can we temporarily
> unlock it and (you or I) commit this?
> Patch log message:
> [[[
> Update references to the issue tracker on our web site to point to JIRA on
> ASF, following the recent migration from Issuezilla on Tigris.
> * www/issue-tracker.html
>   Update to point to the new JIRA issue tracker. Add the new priority
>   keywords against the old priority numbers. Remove obsolete
>   information about requesting 'Observer' role, filing 'Patch' issues,
>   and putting Effort estimates in the Status Whiteboard.
> ]]]

Why do we want to update all this on the old site?

I don't think we really want to maintain javascripts there that points to the new Jira...

My suggestion would be that we should just forward users to the new issuetracker and for the
time being allow access to the historical data.

Scripts to make access to the current issues easier belong on, or on
the Jira instance itself... not on


View raw message