Trac, a project management system reaches its new version Trac 1.4

stage fright

By posting the significant launch of the Trac 1.4 project management system was presented, which provides a web-based interface for working with Subversion and Git repositories, an integrated Wiki, a bug tracking system, and a functional planning section for new releases.

Betweenc is a project management and bug tracking tool written in Python, Inspired by CVSTrac and also distributed under the BSD license, SQLite, PostgreSQL and MySQL / MariaDB can be used to store data.

stage fright takes a minimalist approach to project management and allows the user to automate operations typical routines with minimal impact on processes and rules already developed in the development environment.

The built-in wiki engine allows you to use wiki markup in problem descriptions, goals, and commitments. Supports creating links and organizing links between error messages, tasks, code changes, files, and wiki pages.

To track all events and activities, the project offers an interface in the form of a timeline. In the form of plugins, the modules are available to drive news, create a discussion platform, conduct surveys, interact with various continuous integration systems, generate documentation in Doxygen, manage downloads, send notifications through Slack, support Subversion and Mercurial.

Among its main characteristics, the following can be highlighted:

  • It allows linking information between a software error database, a version control system and the content of a wiki.
  • It serves as the web interface of a version control system such as Subversion, Git, Mercurial, Bazaar or Darcs.
  • It uses a proprietary web template system called Genshi.

tracrpc

Main new features of Trac 1.4

In this new version of Trac 1.4 switching to rendering using the fast Jinja2 templating engine is highlighted, since Genshi's XML-based templating engine has been deprecated, but for compatibility reasons with existing plugins, it will only be removed in the unstable 1.5 branch.

As in previous versions, en this new version the compatibility with previous versions is discontinued with plugins written for Trac versions prior to 1.0. The changes mainly affect the interfaces to access the database.

User groups mentioned in the CC field are automatically expanded in the list of users included in this group. Wiki pages have a switch between displaying narrow-screen and full-screen text.

In email notification templates, it is now possible to use data about changes in ticket fields.

Automatic preview of wiki-formatted text is implemented for all standard fields (for example, report descriptions). In addition, users had the opportunity to independently configure the waiting time between the completion of the input and the update of the preview area.

The TracMigratePlugin plugin has become part of Trac and is available as the trac-admin convert_db command.

This plugin allows you to migrate data from a Trac project between different databases (for example, SQLite → PostgreSQL). You can also observe the appearance of the delete_comment ticket and the attachment movement subcommands.

De the other changes that are highlighted in this new version, the following stand out:

  • Support for cloning tickets (as well as creating tickets from comments) through the optional component tracopt.ticket.clone.
  • Provided the ability to add custom links to the navigation header by regular means.
  • The scope of the change validators has been extended to the batch editing tool as well as the comment editing process.
  • Support for delivering content over HTTPS directly from tracd.
  • Updated minimum requirements for Python (2.7 instead of 2.6) and PostgreSQL (no earlier than 9.1).
  • Custom text fields received the max_size attribute.

Si do you want to use this system project management you can visit the following link where you can find documentation as well as guides for installation, use and especially the download of Trac.


Leave a Comment

Your email address will not be published. Required fields are marked with *

*

*

  1. Responsible for the data: Miguel Ángel Gatón
  2. Purpose of the data: Control SPAM, comment management.
  3. Legitimation: Your consent
  4. Communication of the data: The data will not be communicated to third parties except by legal obligation.
  5. Data storage: Database hosted by Occentus Networks (EU)
  6. Rights: At any time you can limit, recover and delete your information.