Tim, Slavek,
over the weekend I did a full TDE rebuild in Jessie.
The only two packages to fail were compiz-fusion-plugins-main-trinity and compiz-fusion-plugins-extra-trinity, due to a
missing depencency for libjpeg62-dev.
The attached 'control' files fix the problem for both of them. Just rename the files back to 'control'.
Cheers
Michele
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA224
All,
TDE R14.0.0 is now in HARD FREEZE for release. I will be updating the
version number and tagging R14.0.0 in GIT shortly.
Tim
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
iFYEARELAAYFAlSFW2QACgkQLaxZSoRZrGEtOADcD5KX4gEsXqF8h/5GHzLp73AC
9Fuu61fYCQYGFQDfYNjXEmUilYvS0EpjzzolWewZ/Crovjk7BFsvJQ==
=wZeK
-----END PGP SIGNATURE-----
Tim, E.,
whenever I modify a wiki page and click the save button, the page reload and at the top of the page a "question field"
appears. After filling in the answer, I need to scroll to the bottom and press the save button again.
This is cumbersome and a source of loss of time, since the process requires to "save the page" twice and scroll up and
down the whole page.
Would it be possible for the "question field" to be at the bottom of the page and always visible when editing? A good
location would be just below the "summary field".
This would avoid both the additional scrolling and the additional save.
Thanks
Michele
Hi,
I just wanted to share (for fun, not as a tde default) a little tdeui background that I made with Inkscape.
My LG android cellphone has a similar background, and I wanted to see what it looks like on a desktop environment.
Thank you! Tell me what you think!
-Alexandre
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA224
All,
As you can probably see from the activity on the trinity-commits list
there have been multiple updates to both the common cmake/admin modules
and the icons across the entire tree over the past week or so.
This ongoing activity has forced essentially a full archive rebuild for
Debian/Ubuntu, our primary supported distributions.
I am announcing a ***hard freeze*** for R14 to allow the Debian/Ubuntu
rebuild to start generating our RC1 package sets. There are currently
three open bug reports blocking Bug 2014; patches that do not relate to
those three reports must be discussed on this list and approved by me
before being committed to GIT. Additionally, only patches that do not
affect the common cmake/admin modules will even be considered at this
time.
After the RC1 rebuilds are complete this soft freeze will thaw to accept
patches for bugs discovered before and during RC1 testing. This thaw will
be short lived to allow time for RC2 rebuilds, so all patches should be
ready within a week after RC1 release.
Each rebuild cycle takes around 2-3 weeks due to the multitude of
distributions supported. If no common cmake/admin modules are updated for
RC2 the resultant rebuild will take less time.
Onwards to the much-fabled R14 release! :-)
Tim
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
iFYEARELAAYFAlQ9WJAACgkQLaxZSoRZrGEBQgDdFjmryG8MwYCFIAb+KP5tpzPQ
AnbFoau0HP5VAgDfY+1PLlqolGwxLrYhrr06lSQuKbViZ0VpD5vMHg==
=GzuQ
-----END PGP SIGNATURE-----
We have private partial mirrors of various repositories which we
use for testing packages and then to install the packages on each
box. These private partial mirrors are synced nightly.
Because of a bug in lftp we can't use Tim's neat redirector and
instead we mirror Trinity from mirrorservice.org.
Last night there was no change in our partial Trinity mirror.
The night before some old files were deleted but no new files
were added.
The night before that mirroring seemed to be working normally.
It brought in a few dozen files from tdeartwork and tdebase.
Also I see nightly builds updating on mirrorservice.org. I
wonder if RC2 updates are backed up behind nightly build
updates. If so I wonder if it would be better to serve the
volatile but lightly used nightly builds directly so that
the less volatile and more heavily used releases could more
readily migrate to the public mirrors.
--Mike
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA224
All,
TDE will be entering its last hard freeze for R14.0.0 Final at 06:00 GMT
on 12/08/2014. After that time no further commits will be accepted,
R14.0.0 will be tagged in GIT, and pre-release tasks will start.
If you can please help update the release notes at
https://wiki.trinitydesktop.org/Release_Notes_For_R14.0.0
Thanks!
Tim
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
iFYEARELAAYFAlSEq5MACgkQLaxZSoRZrGGzEwDgtSe1JQv8c5vLw3aJ6pydNzVQ
lWR6imB0ROZ/zgDeKVt1LQWRDqdmRQvvuTkEkRUhBNU8VumE9StWZw==
=cs4J
-----END PGP SIGNATURE-----
Tim,
on the main website, there are a couple of things to improve IMO.
1) the link "Bugs" currently points to "https://bugs.trinitydesktop.org/buglist.cgi?quicksearch=ALL" which will
automatically load a long list of bugs resulting in a long loading time. It would be better if it simply pointed to
"https://bugs.trinitydesktop.org" so the loading time would be shorter and the user could choose by him/herself what to
look for.
2) in the mailing list page https://www.trinitydesktop.org/mailinglist.php, I think the "suggestions" about
High/Moderate/Low traffic could be removed. For example the Dev ML has a higher traffic than the User ML, but the
"suggestions" are saying the opposite.
Just my 2 cents.
Cheers
Michele
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA224
Moving right along R14 RC2 has now shipped!
http://trinity-announce.pearsoncomputing.net/?0::31
This means the merge window for R14 FINAL is now OPEN. Please do not
commit patches directly to GIT without review by either me or Slavek.
Patches that change large portions of the source code will not be merged,
but will be deferred for the first R14 SRU.
***Please remember that there will be no further opportunities for the
general userbase to catch regressions introduced by any patches merged in
this window, so make sure you have get it right the first time!***
This merge window will close 12/07/2014 to allow for R14 FINAL build and
release. Please concentrate all efforts on the unresolved bugs blocking
Bug 2014.
Thanks!
Tim
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
iFYEARELAAYFAlR+OYAACgkQLaxZSoRZrGHM+QDbBGJsUqXXUikDXuH6gXuCoL2H
mbUUGSTbwmCcZADdFj3JvAHT5DS8X1kXusb1SfAR7lvfAh25jINW+g==
=vFYc
-----END PGP SIGNATURE-----
