On 9 March 2015 at 15:15, alaninmcr <[email protected]> wrote:
>> As part of this I would also need to migrate the existing issues that >> are in multiple projects into a single project - as I think we agreed >> on this list some time in November to only keep only the Jira project >> TAV at Apache, rather than keep SCUFL2 and TAVSERV separate. > Agreed. There is also TAVUTILS for the DataViewer and CommandLineTool. It is > almost empty though. Done - all unresolved issues from TAVSERV, SCUFL2 and TAVUTILS moved to the T3 project, where they received new bug numbers. I assigned components like "Taverna Language" and "Taverna Server". Jira is good citizen and remains redirection from the old URLs: Example: http://dev.mygrid.org.uk/issues/browse/TAVSERV-265 now redirects (in Jira) to http://dev.mygrid.org.uk/issues/browse/T3-1344 and will HTTP redirect (in Apache) to something like: https://issues.apache.org/jira/browse/TAV-846 Are we still OK with the "TAV" Jira project key? The Taverna 1 bugs (which we'll leave behind!) use the same prefix TAV: http://dev.mygrid.org.uk/issues/browse/TAV-781 I personally feel that "T3" is not appropriate within all of Apache - yet Jira names tend to be short as they'll be used a lot in emails and commit messages. The new key could also be "TAVERNA" -- see existing ones at Apache: https://issues.apache.org/jira/secure/BrowseProjects.jspa#all (Hm - Clerezza and Flink are still incubating there!) -- Stian Soiland-Reyes Apache Taverna (incubating) http://orcid.org/0000-0001-9842-9718
