Release Notes For 3.5.13.2

From Trinity Desktop Project Wiki
Jump to: navigation, search

Trinity 3.5.13.2 SRU is a stable release update that has been an ongoing effort for many months. Many patches from our development channel were backported to the 3.5.13 tree to provide a more stable release for users. This release incorporates over 530 patches and has over 90 reported bugs fixed.

Original 3.5.13.1 Release

The release notes from the original 3.5.13.1 release, on which 3.5.13.2 is based, are available here

New 3.5.13.1 Release

This section highlights some of the most useful improvements to the Trinity system.

Trinity 3.5.13.1 Desktop Trinity 3.5.13.1 Konqueror

Many bugs have been fixed and features added; a partial list follows.

Improvements

  • SAK (Secure Attention Key) improvements
  • Desktop locking improvements
  • Taskbar improvements
  • Kickoff style menu improvements
  • Faster session termination
  • External improvements include support for:
    • automake 1.13
    • clucene 2.x
    • libwpd 0.9
    • mp4v2
    • ruby 1.9
    • xine 1.2

A full list of changes can be found on the full changelog.

KDE4.x compatibility

Trinity can be installed alongside KDE4.x with no problems. Trinity automatically detects and adjusts for KDE4.x programs, so that users can easily run KDE4 applications from within the Trinity environment.

Assisting the Project

If you are interested in helping out, please contact:

Timothy Pearson

A Bluetooth developer who could re-activate Trinity's Bluetooth functions would be greatly appreciated!

Known Issues

None at the moment.

Mailing List

There is a mailing list for Trinity users available here: http://trinity.pearsoncomputing.net/mailing_lists This is a great place for users to share tips and tricks, and you can also sign up to receive announcements related to Trinity.

Feedback

We want to hear what you think about the current release of Trinity. We want to know if it Rocks, if it is just OK, or if it is flat out wrong. No matter the feedback, as long as it is in line with the FOSS Code of Conduct, we would like to hear it.

So what are you waiting for? Head on over to the Feedback Page and let us know!