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
Trinity Desktop Environment version 3.5.12 has been released! This
version provides significant enhancements to areas such as Personal
Information Management (PIM), GTK application support, and general
usability.
You will find a detailed list of upgrades and improvements to the Trinity
system here:
http://trinity.pearsoncomputing.net/wiki/bin/view/Documentation/Releases_3_…
Installation instructions for Debian, Ubuntu, and Slackware are available
on the Trinity project home page:
http://trinity.pearsoncomputing.net/
If you would like to compile Trinity from source instead of using the
prebuilt binaries, instructions are available here:
http://trinity.pearsoncomputing.net/wiki/bin/view/Developers/HowToBuild
And the source itself can be downloaded from the main project Website at:
http://trinity.pearsoncomputing.net/
Simply click on the 3.5.12 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://trinity.pearsoncomputing.net/mailing_lists/
This release was the result of collaboration between several open source
developers; their names are listed at
http://trinity.pearsoncomputing.net/contributors/ The Trinity project
would like to thank them for their support!
Be sure to let us know what you think of this release, and enjoy!
Timothy Pearson
Trinity Desktop Project
As of 1:00PM CDT on September 27, 2010 a hard freeze is in effect in SVN.
Only crash fixes will be accepted at this point, and only if the patch
will not affect any other sections of Trinity.
Also, this is a friendly reminder that release is in less than 4
days...distribution maintainers, get your build systems cranked up!
Timothy Pearson
Trinity Desktop Project
As of September 21, 2010 a pre-release freeze is being declared for
Trinity version 3.5.12.
This means that patches will only be accepted into SVN for the following
reasons:
1. To repair a crash
2. To repair broken functionality, if the patch is very small and impact
to other code is minimal.
3. To disable broken features, if the patch required to repair the broken
feature does not fit into category 2 above.
This freeze means that the following patches, among others, will NOT be
accepted during the freeze period:
1. Changes to log messages, including warning and informational messages.
2. User-visible interface changes of any kind.
As with the feature freeze, this freeze will end on October 1, 2010 with
the release of 3.5.12.
I encourage everyone to update to the latest SVN release and start testing
to ensure that the software is stable and all features work as intended.
Thanks to the Trinity developers for all your hard work!
Timothy Pearson
Trinity Desktop Project
This is a friendly reminder that a feature freeze for Trinity 3.5.12 is
now in effect. All developers should update their SVN to the latest
revision, rebuild, and start testing to find any major bugs prior to
release.
Also, searchable Qt3 and Qt4 documentation is up on the Trinity website at
http://trinity.pearsoncomputing.net Click on the "Documentation" link on
the left hand side to reach the new documentation page. Work is also
ongoing to rebuild an API documentation page for Trinity itself through
Doxygen.
Please remember to report any major bugs found to the trinity-devel list!
Timothy Pearson
Trinity Desktop Project