Savannah version 1.3 release note

Apart from fixing a number of bugs, this new version provides two new features.

A cookbook manager based on the savane tracker engine is now available. This new feature implements an environment to submit, edit and browse 'recipes' for one's project. It is therefore available to both user projects and to LCG Savannah itself to help users.

The infrastructure is now in place with the installation of this new version of Savane. The Savannah cookbook will be gradually populated as new documentation will be written.

The cookbook item submission and edition are done in a way similar to what is done with the other trackers.

Since recipes should be easy to access and to read, a list organised per feature and per audience is accessible both via the 'cookbook' item of the project public menu and via the cookbook icon shown in the middle of the project homepage. The recipe pages display the appropriate information plus indications of the:
  • audience
  • features
  • related actions
they apply to.

An export feature is now available via a new 'export items' submenu in the four trackers. Users select items to be exported in the same way as they specified selection criteria to browse items. In addition they must specify when the export should take place (as soon as possible / at a given time today or in the coming month) and if it should be done once only or every so often.

The export process being heavy on the server, it has been implemented as a two step process:
  • export requests get specified and posted via the submenu mentionned above.
  • a cronjob watches once an hour pending export requests, process them and write the resulting xml files at the location shown to the requestors on the export page.
This approach avoids premature abortion of long exports (php aborts pages which take more than 30 sec to be served) and allows processing of Savannah requests while export files get built in the background.

The users can watch on the export page when their request switch from pending to done. Once it's done they can download the resulting xml file by clicking on the corresponding link and afterwards they can delete the server based instance of the file by clicking the corresponding icon.

The export file contains all the used fields of the selected items as well as the history of items. At present the files possibly attached to items are not exported.