Trevor Daniels wrote Wednesday, May 06, 2015 10:05 PM
I'm just importing the issue DB at the moment.
I've now tried twice to import our Issue DB from GoogleCode to Allura at
SourceForge. As previously reported the first attempt failed after 1112
issues. The second attempt also resulted in a failure message, but it
actually appears to have imported pretty well all the issues. 4369 issues
were imported, and the highest numbered one, 4377, corresponded to the
highest numbered issue in GoogleCode at the time. In neither case was any
reason for the failure message given, and SourceForge support have not
responded to an email querying the failure in over a week.
This is good news, I think. However, the second import took around 36
hours, and this at a time when (presumably) few others were trying to
export data from GoogleCode. Wherever we finally decide to move our
Issues DB to, I would strongly suggest we do not wait until the day
GoogleCode moves to read-only (24 Aug 2015). Everyone one will be
migrating then, and the time required is likely to be much larger, and
reliability may also be affected. I would suggest we aim to freeze our DB
2 weeks before read-only, i.e. on 10 Aug 2015, and start the migration
then. Hopefully that way we'd avoid the last-minute congestion.
As to the match of Allura to our needs, AFAICS it can provide everything
in Phil's requirements list except for the automatic handling of blocked
issues. I'll double check this over the next few days and report point by
point.
Trevor