Re: Scarab user

Hi;

I think, Scarab is constantly developed over time by a couple of 
enthusiastic developers.
But the development speed varies significantly. I myself have been 
almost absent for nearly 2
years but currently i am working again intensively on this tool because 
i need to stabilise some
basic functionality and make it overall better suitable for a job in a 
production environment
You can see my recent development either in this forum, or in the 
development forum,
or in the Scarab selfhost. Also if you want to see Scarab in action, 
look at the Selfhost.
It currently is in synch with the trunk, maybe sometimes on revision 
behind ...

Concerning releases: there is currently a slowly ongoing move to 
stabilise the 0.22 branch for
delivery. I am not sure about the state of this and when it finaly gets 
released. I myself rely on
trunk and i am using the current trunk within my production environment. 
It is the best test environment
i can get, because the customer is very patient and helps a lot to 
identify problem zones and find
working solutions.

Here is my list of tasks which i was working on during the last 3 months 
and will continue for
a couple of weeks:

- enhance the notification system, (done, now significant better 
information on the subject line)
- short links for queries (done, now calls to queries are almost as easy 
as calls to issues)
- improvements on the personnel editor (in queue)
- postprocessing of attribute entries directly after entry (on browser 
side, in queue)
- Support for Creole-1.1 (done, standard wiki syntax)
- Support for skins (partially done)
- many new features concerning display of attributes (done, 
documentation needed)
- fix of incorrect display of attribute values (partially done for Date 
in search results)
- Support for views (working, but not yet committed)
- Enhancements in the navigation system (left navigation bar 
significantly imroved)
- Many small changes and bugfixes

I think that once i am finished with my work (should be done by end of 
july 2009) trunk will be
release stable and tested in a production environement. I am not sure 
though if that will become
a release 0.23 ...

The main reason, why we do not have frequent "releases" is that 
typically trunk is reasonably stable
and it can be used in production. Sometimes it needs fixing in special 
use cases, which are not frequently
used/needed, but overall IMHO it is a stable system (at least for MySQL 
and on linux based hosts, for other
environments i can not tell, but i guess it is equivalent stable)

Hope that helps you a bit ?
If you want to give it a try, checkout trunk and go. If you need to 
upgrade, take care, there are some
database changes to be applied, see src/sql/upgrade/upgrade-*.sql

More questions ?
ask ;-)
Hussayn

Lander Freitas wrote:
> Hi,
>
>   
>> We have the 2005 version installed and will update to the 2007 version, 
>> but
>> I was questioned if the project been discontinued?
>> We have been tasked to find out why there aren´t "newer" versions of the
>> Scarab software.
>>
>> Thanks.
>> Lander
>>
>> -------------------------------
>> Lander Freitas
>>
>> Analista de Testes
>> Conab - Companhia Nacional de Abastecimento
>> Brasília, DF
>> [email protected]
>> Fone: (61) 3312-6443
>>
>> ------------------------------------------------------------------------------------------------------------------------------
>> Antes de imprimir, pense em sua responsabilidade para com o MEIO AMBIENTE.
>>
>>     
>
> ------------------------------------------------------
> http://scarab.tigris.org/ds/viewMessage.do?dsForumId=456&dsMessageId=2361044
>
> To unsubscribe from this discussion, e-mail: [[email protected]].
>   


-- 
Dr. Hussayn Dabbous
SAXESS Software Design GmbH
Neuenhöfer Allee 125
50935 Köln

tel.: +49 221 560 11 0
fax.: +49 221 560 11 20

mailto:[email protected]
http://www.saxess.de
http://www.saxess.com
http://www.saxess.org

------------------------------------------------------
http://scarab.tigris.org/ds/viewMessage.do?dsForumId=456&dsMessageId=2361092

To unsubscribe from this discussion, e-mail: [[email protected]].