[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: ASF JIRA migration: Update our Tigris and Apache web sites

From: Julian Foad <julianfoad_at_gmail.com>
Date: Sat, 3 Oct 2015 10:16:09 +0100

Bert Huijben wrote:
> Julian Foad wrote:
>> 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 subversion.apache.org, or on the Jira instance itself... not on subversion.tigris.org.

Your suggestion sounds good to me. A new patch is attached, which just
redirects to the subversion.a.o/reporting-issues.html.

- Julian

Received on 2015-10-03 11:16:53 CEST

This is an archived mail posted to the Subversion Dev mailing list.