[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Moving the Issues DB to Allura
From: |
Trevor Daniels |
Subject: |
Re: Moving the Issues DB to Allura |
Date: |
Wed, 26 Aug 2015 18:36:00 +0100 |
Han-Wen Nienhuys wrote Wednesday, August 26, 2015 12:22 PM
> I'm kind of surprised that you ended up going to sourceforge, whereas
> github was discarded because it wasn't a Free enough solution.
I don't think that was the only reason:
> Error "Project cannot be migrated because it has too many issues."
> There is a hard limit on the number of issues that can be exported by the
> tool, per repo. > If your project has more than 1,000 issues the export will
> fail.
We have over 4,000. With image attachments.
Allura is OS and its import tool imports our DB out of the box, including
attachments. The intention was, still is, to install Allura in a VM on a
Savannah server. But that's going slowly, so SF is a stop-gap host. Quite
useful as it happens, as the Allura devs are there and are proving responsive
and helpful.
> Now I'm greeted with ads as I go to the project page.
SF is hardly more commercial than Google anyway, although the ads are a
nuisance, granted.
Trevor