lilypond-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Moving the Issues DB to Allura


From: Phil Holmes
Subject: Re: Moving the Issues DB to Allura
Date: Wed, 26 Aug 2015 21:06:29 +0100

----- Original Message ----- From: "Trevor Daniels" <address@hidden>
To: "Han-Wen Nienhuys" <address@hidden>
Cc: "Lily-Devel List" <address@hidden>
Sent: Wednesday, August 26, 2015 6:36 PM
Subject: Re: Moving the Issues DB to Allura



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

Good point. Complaining from Google that a site overuses advertising is very pot-kettle.

--
Phil Holmes



reply via email to

[Prev in Thread] Current Thread [Next in Thread]