Apologies for letting this slip - I think it's getting urgent to get our JIRA sorted now to keep track for everything as we're getting over the hurdle of moving the source code and need to build the first releases.
Jira is pending on Manchester sysadmins (e.g. me) to prepare the JIRA dump for INFRA to import. I talked to INFRA about this at ApacheCon - we need to have a blank JIRA project at Apache and hand them a full Jira backup dump, and then they can selective import just one of the projects. Before the Software Grant we were not formally allowed to move this. Another reason I have not had a look at this yet is that I need to move the issues info a temporary instance locally that is at a matching version as that at Apache - our current instance at http://dev.mygrid.org.uk/issues is outdated (and for some reason Atlassian has not given us a new license key for Jira yet, so I'll have to use an evaluation version for the move). 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. So it's just one of those tedious tasks that has been too easy to delay.. :-/ On 9 March 2015 at 14:52, Andy Seaborne <[email protected]> wrote: > Hi there, > > Where is the podling on getting a JIRA project setup? > > https://issues.apache.org/jira/browse/INFRA-8637 seems to be waiting on the > podling. > > Andy -- Stian Soiland-Reyes Apache Taverna (incubating) http://orcid.org/0000-0001-9842-9718
