[Pkg-giraffe-discuss] WebApp 2.1.0 RC1 released

[Carsten Schoenert]

Heads up,

I've done some more rework to import a cleaned out version of the the
last 2.1.0 RC1 version based on the discussions from last Thursday.

It's not uploaded to Alioth because I suspect some remaining issues
which should be fixed before. I pushed the current state again to

https://github.com/tijuca/zarafa-webapp

If you build this current state with a recent version of lintian you
will notice the error list is now becoming larger than before (but don't
worry). The maintainer of lintian have implemented some stronger checks
against probably non source JS files after a long discussion on
debian-devel. If you have enough free time the whole loooong thread can
be read here:

  https://lists.debian.org/debian-devel/2015/08/msg00427.html

It seems the last changes for lintian about the JS source checking are
needing some more fine granularly to don't bother user with false
positive messages. There is already opened up a bug for this:

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=798900

If the lintian package is fixed there is only a warning about the
tinymce package left which couldn't be resolved without updating the
tinymce package itself.

The other issues which were visibly in in version 2.1.0~beta1 are now
resolved by dropping the folder
plugins/files/php/Files/sabredav/vendor/sabre which was including the
some *.php files with a shebang but without execution rights (and these
files aren't needed).

And the more critical thing, a PHP-2.02 licensed 'timezones.inc' file
could be also dropped, also don't needed.

It would be a good thing if this two removes of folders could go into
the final release to not differ that much, in particular these files and
folders are also not needed inside a Zarafa release. Within the commit
you find this two folders that are removed (one while recreate the
upstream tarball, the other while running dpkg-buildpackage)

  plugins/files/php/Files/sabredav/vendor/sabre
  plugins/spreed/php/dat/legacy

To go further Guido suggested to implement some tests based on selenium.
I haven't any experience with Selenium so I can't do much here.

-- 
Regards
Carsten Schoenert