Re: [Kolab-devel] Kolab 3.3 feedback

Hi Jeroen

here's some feedback, but bear with me, I tested it on a clean Debian7 
VM. So I don't know wether there's a bug or there's a packaging error. I 
would have started to see if it's a real debian packing problem or a 
real bug, but the OBS Systems seems to be down. It won't let me branch a 
package to fix a simple thing like the missing itip module in pykolab 
(already reported).

At some point I stopped reporting bugs cause I couldn't find the right 
product in the new organized bugzilla ...

Maybe I should start testing on Centos first, but my life system runs 
debian, so I'm interested in getting the debian version running so I can 
do a test migration.


Here's the list:

# setup-kolab

2014-08-07 00:54:09,422 pykolab.conf ERROR Could not change permissions 
on /var/log/kolab/pykolab.log: OSError(2, 'No such file or directory')

Old bug but still present: https://issues.kolab.org/show_bug.cgi?id=2798
Likely not critical but people will still see it.


# wallace

itip module missing

Known bug: https://issues.kolab.org/show_bug.cgi?id=3250
Simple packaging fix, but OBS seems to not work right now

oh btw, I would like to test wallace and resource booking within the 
calendar, but the documentation doesn't provide an example on how 
wallace has to be integrated. Or which process decided that the 
invitation email of a resource has to be forwared to the wallace daemon 
on 10026

Is it just configurig the content-filter in the section 127.0.0.1:10025 
of the master file to content_filter = smtp-wallace:[127.0.0.1]:10026?


# Mixed character sets for new created database tables

Verious tables (kolab_alarms and all syncrotron) have "no" exlicit 
characterset configured in their initial file (which takes system 
default which could be different then all the other tables). It's not a 
big issue but this "could in theory" be a problem someday.
There's even one table in roundcube itself that has no specific charset 
configured instead of utf8.
Reported: https://issues.kolab.org/show_bug.cgi?id=3262


# kolab-webadmin

## shared folders

IMAP Access Rights > New
Uncaught TypeError: Cannot read property 'match' of undefined 
example.com/kolab-webadmin/js/kolab_admin.js:1897

Line: 1897: 
subject_select.val(acl.subject.match(/^(anyone|anonymous)$/i) ? 
acl.subject : 'user').change();

Can't report the problem, cause I can't open a Bug for the product Web 
Administration Panel / user interface


# roundcube

## config

the default kolab_addressbook.inc.php is a duplicate of config.inc.php. 
The config is correct in the roundcubemail-plugins-kolab debian package. 
likely in postinst something ist wrong.

## no folders

* no folders are visible in the folders section in all modules like 
mail, contacts, calendar, etc
* folders are visible under folder management
* this causes all kinds of strange results

## right click mail message

Uncaught TypeError: Cannot read property 'ml' of undefined 
contextmenu.js?s=1391242078:274

273: var msg = rcmail.env.messages[matches[1]];
274: if(!msg.ml)

## Notebooks

Create a notebook, it doesn't appear (caue no folders are shown). It's 
not visible under folder management but "kolab lm" will show it.

## Tags

not enabled per default in config.inc.php? That's inteded cause it's too 
new? Can't test it right now cause something is wrong with the 
contextmenu

=====

well ... that's all for today. maybe we can get things looked at in the 
next days, I know this is a pretty short test cycle for a beta before 
the release gets its "stable" marker.

P.S. if you really want to get things tested before you declare a 
version as "stable" I would recommend to give the community more time to 
test ... especially in the summer where lots of people are likely on 
vacation.


--
Kind regards,
Daniel Hoffend



------ Originalnachricht ------
Von: "Jeroen van Meeuwen (Kolab Systems)" <[email protected]>
An: "Kolab Development Coordination Mailing List" 
<[email protected]>
Gesendet: 04.08.2014 01:40:18
Betreff: [Kolab-devel] Kolab 3.3 release forthcoming

>Hi there,
>
>As mentioned in the other email, we have a pending release of Kolab 3.3 
>this month, at or around the 14th (which is six months after the Kolab 
>3.2 release on Valentine's day, henceforth to be referred to as Kolab 
>Release day).
>
>From experience (and from looking at my agenda) I know it's *NOT* going 
>to be the 14th, rather after the following weekend (the 19th or 20th).
>
>Also from experience, I'm asking you to get your bug reports in *NOW*;
>
>   - use Kolab:Development to install what is to become Kolab 3.3, if at 
>all possible (otherwise, log bug),
>
>   - test functionality -- most things have had one or another change,
>
>   - those with the ability to test upgrades, please do -- especially 
>with regards to existing mail spools.
>
>I'm looking forward to your reports of failure, I'll take every single 
>one of them as a compliment ;-)
>
>That said, if you report one and I go "oh, nice catch!", you've earned 
>yourself a beer.
>
>Kind regards,
>
>Jeroen van Meeuwen
>
>-- Systems Architect, Kolab Systems AG
>
>e: vanmeeuwen at kolabsys.com
>m: +44 74 2516 3817
>w: http://www.kolabsys.com
>
>pgp: 9342 BF08
>_______________________________________________
>devel mailing list
>[email protected]
>https://lists.kolab.org/mailman/listinfo/devel

_______________________________________________
devel mailing list
[email protected]
https://lists.kolab.org/mailman/listinfo/devel