newsSavane - News: Release 1.0.7: getting unicoded!

 
 
Show feedback again
Latest News
New Savane release fixes symlink attack and privilege escalation posted by beuc, Wed 02 Dec 2009 10:24:18 PM UTC - 0 replies
Release 3.0: markup language and anti-spam tools posted by yeupou, Mon 04 Dec 2006 09:38:30 AM UTC - 2 replies
Release 2.0: interface heavy improvements, bugfixes and cosmetics posted by yeupou, Tue 03 Oct 2006 08:06:29 AM UTC - 2 replies
We need packagers! posted by yeupou, Tue 19 Sep 2006 06:09:45 PM UTC - 2 replies

Release 1.0.7: getting unicoded!

Item posted by Mathieu Roy <yeupou> on Thu 30 Jun 2005 03:05:55 PM UTC.

I'm glad to another 1.0.7 savane release. Thanks a lot to Tobias Toedter, the major actor of this release.

The release tracking has been made with the task #1481.

Obtaining it:
-------------

- The GPG-signed tarball is available at <http://download.gna.org/savane/>
- It is downloadable via CVS, with the tag REL_1-0-7
- You can use apt-get with Debian, adding "deb http://dl.gna.org/savane/debian/ stable/" (without quotes) in your /etc/apt/sources.list

Main purpose of the release:
------------------------------------

The purpose of this release is to switch to encoding UTF-8.
Why doing that? Simply to avoid clashes when users are writing different languages that require encoding different from the usual iso 8859-15 (bug #2251, bug #2257, bug #2307, bug #2440).

This implies:
- update of site specific content to UTF-8
- update of the database content to UTF-8

Every aspects of the upgrade process are, supposedly, covered by the README file in update/1.0.7.
Read carefully this file.

Even if you do not expect your users to speak anything apart iso 8859-15 encoded language, you are strongly encourage to perform the upgrade, since future releases will anyway be fully in UTF-8.

Installing it/Upgrading it:
-------------------------------

If you are running Savane 1.0.6, you should run sql and perl scripts included in savane/update/1.0.7, as described in savane/update/README (or shipped with the debian package savane-update).
These scripts will handle the trivial changes on the database needed. They are supposedly safe but you should, indeed, do a backup of your database first, just in case (using mysqldump, for instance).

If you are running an older version than 1.0.6, you should run the scripts in savane/update for each release you missed.

Also, take care to the sections [CONFIGURATION] and [SITE SPECIFIC CONTENT] of the
ChangeLog below, it will tells you which files should be added in your site specific content directory.

Otherwise, just follow INSTALL, or INSTALL.verbose if it not enough. If you encounter undocumented troubles, please fill a support request at <https://gna.org/support/?group=savane>

ChangeLog :
---------------

Below are the change/new features you may be interested in. This is almost an exhaustive list of changes by topic.

[CONFIGURATION]

The configuration setting sys_top_dir has been replaced by
sys_www_top_dir.
While sys_top_dir was the path to the Savane package top directory,
sys_www_top_dir is the path to the www frontend. Which means in most
case sys_www_top_dir = sys_top_dir/frontend/php.

This change has been made necessary for packaging purpose where there's
no longer any relevant "top directory".

It means that you have to recreate/update your configuration file
using sv_update_conf.

[OVERALL]

The purpose of this release is to switch to encoding UTF-8.
Why doing that? Simply to avoid clashes when users are writing
different languages that require encoding different from the
usual iso 8859-15 (bug #2251, bug #2257, bug #2307, bug #2440).

This implies:
- update of site specific content to UTF-8
- update of the database content to UTF-8

Every aspects of the upgrade process are, supposedly, covered by
the README file in update/1.0.7
Read carefully this file.

Even if you do not expect your users to speak anything apart iso
8859-15 encoded language, you are strongly encourage to perform the
upgrade, since future releases will anyway be fully in UTF-8.

[FRONTEND]

  • During the project registration, no group type is selected by

default any longer. Users are now asked to select a group type.
This change was wanted by GNU Savannah in order to avoid having
plenty of groups selecting GNU Type just because it was the
default (bug #2289).

  • CC-list is now show after item dependancies, in item details

(bug #2169).

  • Visually mention users role related to an item: latest comment

of the assignee is highlighted, show specifics icons for each comment
depending on the fact that the comment author is member or admin of
the project (bug #2170).

  • Cleanups of the default query reports. Among several changes, note

that the "bug id" form has been removed. It was added as workaround
back in the days when search forms where unable to find items given
their number. This is no longer true and since it would require
non-trivial change to have this form item behaving cleverly
(for instance being able to find more than one item at a time), it is
best to recommend usage of the search feature, when people are looking
for an item given their number (bug #2194, bug #2195).

  • Add default status value "Confirmed" for support and bug trackers.
  • Properly guess archives name with numeric characters (perl

frontend).

  • New page that list GPG keys registered in the group keyring, if any,

and that allows to download this keyring.

[BACKEND]

  • Removal of admin/sv_registerx_discard.pl (bug #2230).
  • Fix a bug causing urls sent by sv_reminder to be broken if

$sys_url_topdir is different from "/" (bug #2516).

  • sv_users now creates group gpg keyrings, if started with the option

--gpg-group-keyring
This option has not been heavily tested. We noticed some unexplained
yet failure, if you need to use this option, it could be useful in
cronjobs to add a another call to sv_users, but without this option,
first (task #1926).

  • sv_gpgcheckfiles added, a script that could make GPG checks

on download area content. See --help for more details.
This script is provided as it is, has not been heavily tested
(task #1926).

[LIB]

* Savannah.pm has finally been renamed Savane.pm for consistency.

-----------------------

That's all folks!

Comments:

Small issue (posted by Mathieu Roy, Fri 01 Jul 2005 07:41:09 AM UTC)

A small typo was found in savane-lib (Savane::Mail) causing mails sent by sv_reminder to be malformed.
Packages have been rebuil and cvs tagged REL_1-0-7a

[ Reply ]


   

 

Start a New Thread:

You could post if you were logged in
Show feedback again

Back to the top


Powered by Savane 3.1-cleanup