[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Assessment of Allura at SourceForge
From: |
Federico Bruni |
Subject: |
Re: Assessment of Allura at SourceForge |
Date: |
Fri, 22 May 2015 13:17:57 +0200 |
Hi Trevor
Many thanks for taking up this task
Il giorno gio 21 mag 2015 alle 0:19, Trevor Daniels
<address@hidden> ha scritto:
I'm becoming increasingly concerned about the loading of Allura at
SourceForge, maybe due to other projects attempting to migrate from
GoogleCode. After exporting our Issues DB on Sat evening and
modifying the Post authors to "GoogleImporter" I attempted to
re-import it. During Saturday evening, all day on Sunday, and early
on Monday my attempt was rejected due to the load on the server. The
import request was finally accepted on Monday afternoon, but failed
after loading about a quarter of the issues. No details given. I
initiated the import again late on Monday evening, and this had
completed successfully by early Wed morning, after running for 33
hours. So weekends are a dead loss, and altogether it took me almost
5 days just to re-import the DB.
Furthermore, I've observed today that searches are frequently
rejected with "Errno 111 Connection refused", another symptom of
server overload.
Maybe we need to pursue an alternative server to SourceForge urgently.
The import script will work if you install Allura on your computer?
It may be easier to test and import locally and then update to the
server we eventually decide to use.
I'm in the process of tailoring a test facility for developers and
admin to play with, and as a vehicle for re-engineering git-cl and
patchy. I'll post again when this is ready.
In spite of the frustrations I have prepared a test bed for
developers, admins, bug-squad and users to play with. It's at
https://sourceforge.net/p/testlily/tickets/ . It is populated with
the all the Issues from GoogleCode up to around 7 May 2015. I've
added all the extra fields needed to accommodate our practices and
created several useful searches. This is what it would be like after
migration.
*** We now need others to try all the actions they would normally do
with the Issues DB to expose any further problems. ***
The labels field just allows to sort alphabetically. It would be
possible to show a list of the labels, as in the Status field?
I find the search syntax uneasy. For example, to add a keyword to one
of your saved search I learned after two fails that I should have
inserted AND before the keyword:
_type:Documentation AND (status:New OR status:Accepted OR
status:Started) AND partcombine
The same search could be (in github for example):
is:open is:issue label:Documentation partcombine
No capital letters, no parentheses, no redundant stuff.
Re: Assessment of Allura at SourceForge, Dan Eble, 2015/05/22