The binary packages for the Trinity Desktop Environment v3.5.13 are now on
the mirror system and ready for installation!
If you run into any problems please don't hesitate to contact us via one
of our mailing lists (http://www.trinitydesktop.org/mailinglist.php) or on
our IRC channel (#trinity-desktop).
Enjoy!
Timothy Pearson
Trinity Desktop Project
As you are probably aware the Trinity website went dark for a sizable
chunk of November 2, 2011. This was due to one of our Internet service
provider's fiber optic lines being cut, and all Trinity services have now
been restored.
However, this event has delayed the publishing of the Trinity 3.5.13
binary packages for all supported distributions. While the complete
3.5.13 source tree is currently available for download, binary packages
will not be available for download until Friday, November 4, 2011 at the
earliest.
The Trinity Desktop Project apologizes for the inconvenience, and hopes
that you will enjoy our latest release in a couple days.
Timothy Pearson
Trinity Desktop Environment version 3.5.13 has been released! This version
provides significant enhancements to areas such as desktop security, GTK
application support, and general usability.
You will find a detailed list of upgrades and improvements to the Trinity
system here:
http://www.trinitydesktop.org/wiki/bin/view/Documentation/Releases_3_5_13
Installation instructions for Debian, Ubuntu, Fedora, RedHat, and
Slackware are available on the Trinity project home page:
http://www.trinitydesktop.org/
If you would like to compile Trinity from source instead of using the
prebuilt binaries, instructions are available here:
http://www.trinitydesktop.org/wiki/bin/view/Developers/HowToBuild
And the source itself can be downloaded from the main project Website at:
http://www.trinitydesktop.org/
Simply click on the 3.5.13 link on the lower left hand side of the screen.
Why upgrade from KDE3.5.10, the latest release available from KDE e.V.?
Simply put, Trinity is faster, more secure, and far more feature rich than
3.5.10 ever was! It incorporates the latest patches from multiple KDE
enhancement projects, such as OpenSUSE, Chakra, and Ubuntu.
If you do find a bug, please don't hesitate to report it to the project
bugtracker at
http://bugs.pearsoncomputing.net/
If you would like to connect with other Trinity users and/or developers,
or simply want to be informed of the latest updates to the Trinity system,
the official project mailing lists are available here:
http://www.trinitydesktop.org/mailinglist.php
This release was the result of collaboration between several open source
developers; their names are listed at
http://www.trinitydesktop.org/contributors.php
The Trinity project would like to thank them for their support!
If you like the Trinity project, why not donate to help keep it alive?
Your contributions help fund both the Trinity project infrastructure and
the development of new features. Details are available here:
http://www.trinitydesktop.org/donate.php
Be sure to let us know what you think of this release, and enjoy!
Timothy Pearson
Trinity Desktop Project
NOTE: Binary packages are currently being uploaded to the worldwide mirror
system. Sources are already available, however the binaries may take a
day or two to become available to all mirrors.
The Trinity Desktop Environment source code is now in a final freeze for
v3.5.13. This means that NO ALTERATIONS of any type will be accepted.
Source tarballs are in the process of being built.
Distribution packagers, now is the time to get your final binary packages
built for release. If you encounter any build failures on your
distribution you will need to patch around them via your build scripts.
As a reminder, the official 3.5.13 release will occur on November 1st,
2011. Official binary packages for Debian Squeeze, as well as Ubuntu
Lucid through Oneiric will be available at that time. No Ubuntu LiveCD
respins will be available on the release date, and LibreOffice packages
for Oneiric are pending upstream patch acceptance into the LibreOffice
project.
Tim
Hello,
Here are some further notes regarding the 3.5.13 release. The release
is on schedule for Nov 1st (in 3 days).
Now is your last chance to send in patches for the release. After Oct
29th a hard freeze will be in effect. No changes past this point will
be made. This is to ensure that packagers have enough time to produce
packages. After that the final tarballs will be built for the release.
For the 3.5.13 release there will be no Ubuntu LiveCDs. If someone
would like to respin a LiveCD for us, we will be happy to host the
files.
Oneiric packages are built and ready to install. Please report any
problems you find.
For Oneiric installation instructions:
http://www.trinitydesktop.org/wiki/bin/view/Developers/NightlyBuilds
Lastly, LibreOffice integration will not be available in Oneiric until
the creation, submission, and incorporation of patches into the
upstream LibreOffice project.
Thank you,
Calvin Morrison
Trinity Desktop Team
The Trinity code repository is officially in a hard freeze as of 6:30PM
CDT 10/25/2011, pending release of TDE 3.5.13. The only updates that will
be accepted at this point are critical bug fixes that require only minor
changes to the TDE source.
Distribution packagers, start building your official packages for release
at this time. We are on schedule for an official 3.5.13 release on
November 1, 2011.
Timothy Pearson
Trinity Desktop Project
Hi all,
Next Meeting is currently set for 19 or 20 of April. If nobody reponds
to available times here http://www.doodle.com/eivtcn5c3wndqt2u , I
will assume 2PM EST. Deadline for submitting available times is
Saturday.
Meeting topic list also needs to be updated, see
trinity.etherpad.trinitydesktop.org/19 or bring it up on
#trinity-desktop by pinging Xu_R, samelian, kb9vqf, or MutantTurkey.
If you have write permissions, please alter the etherpad.
Trinity users are invited for input this meeting.
*AS ALWAYS*, meetings are in #trinity-desktop-meeting and the channel
is unlocked 24 hours before meetnig.
--
later, Robert Xu
Hello,
Trinity is currently undergoing a conversion from Automake to Cmake.
We are making this change because the Automake build scripts have broken
with recent versions. Cmake is saner and easier to manage, especially
with larger projects, such as Trinity. This conversion is critical to TDE
because Automake is a major blocker for the 3.5.13 release. After we have
converted to the Cmake system, building and maintaining Trinity should be
smoother and simpler.
We are looking for anyone with Cmake experience, or anyone willing to
learn, to come forward and help us with the conversion to Cmake.
Thank you,
Calvin Morrison
On behalf of the Trinity Development Team
Hello,
Trinity is currently undergoing a conversion from Automake to Cmake.
We are making this change because the Automake build scripts have broken
with recent versions. Cmake is saner and easier to manage, especially
with larger projects, such as Trinity. This conversion is critical to TDE
because Automake is a major blocker for the 3.5.13 release. After we have
converted to the Cmake system, building and maintaining Trinity should be
smoother and simpler.
We are looking for anyone with Cmake experience, or anyone willing to
learn, to come forward and help us with the conversion to Cmake.
Thank you,
Calvin Morrison
On behalf of the Trinity Development Team
Hi all. This is a post to clear up any issues that people might be
confused with.
We've all agreed to this, so this is now here for reference.
So, let me start of by saying:
TRINITY IS NOT KDE3 (anymore).
KDE3 IS DEAD.
And let me go a bit further with that.
We are currently in an alpha stage of porting Trinity to cmake.
There is currently the following in usable or finished states:
- tqtinterface
- arts
- kdelibs
- kdebase
- kdedevelop
The 3.5.12 tarballs DO NOT have them. I repeat, DO NOT have cmake scripts.
You will need to download them from http://thel.ro/ and insert them
into the build directory.
We are also in a pre-alpha stage of porting Trinity to Qt4.
Before I go any further, let me say:
WE ARE NOT PORTING APPLICATIONS ONE BY ONE TO QT4 (as may have been
interpreted before).
What we are doing is porting the apps to TQt (a relatively easy thing
to do), and then letting TQt handle the Qt version specifics.
TQt for Qt4 has been progressing along for some time, although it is
COMPLETELY FAR from stable.
If you'd like to see a screenshot from 3.5.13, Tim provides one here:
http://tinypic.com/view.php?pic=1586qmp&s=7
I assure you, we are not making another KDE4. We'll leave that junk to
the KDE4 developers.
Thank you for taking the time to read this.
Robert Xu
On behalf of The Trinity Development Team
