Message: previous - next
Month: December 2011

Re: [trinity-users] Upgrades to TDE 3.5.13 ...

From: Jorge Gonçalves <jmg.correio@...>
Date: Mon, 5 Dec 2011 08:04:41 -0200
On Sun, Dec 4, 2011 at 7:30 PM, Timothy Pearson
<kb9vqf@...> wrote:
>> On Sat, Dec 3, 2011 at 9:19 PM, Timothy Pearson
>> <kb9vqf@...> wrote:
>>> Most likely you will have to wait for the next release.  I assume you
>>> have
>>> bug reports in for the problems you are experiencing?
>>> Tim
>> Hi Tim,
>> Although Trinity is great and is already very stable, you had
>> previously recognized that the TDE 3.5.13 release lacks some
>> polishing.
>> So, if some bugs and corrections are being done by the devs, why not
>> let the users get them now, instead of waiting 6 or more months?
>> The point here, is that with Debian, people are used to get new
>> upgrades, new versions, and more important, bug corrections via
>> apt-get, _all the time_.
>> So, maybe Trinity lacks here is a maintainer for the Debian packages,
>> so that they can been regularly upgraded, at least if not with new
>> features, with bug corretions and general polishing??
>> Thanks.
> At this point it is a combination of several factors:
> 1.) What you have mentioned already; that is, I am the defacto Debian
> maintainer and don't have much free time.  QuickBuild should allow an
> interested maintainer to step up and start working on this part of the
> project without much difficulty.
> 2.) The fixes simply aren't in GIT yet.  The GIT transition is scheduled
> to be finished by the end of December.
> 3.) During the GIT transition we are renaming a bunch of *KDE* strings to
> *TDE*.  This makes it extremely difficult to fire off a build from the
> sources in GIT and actually have it work with the 3.5.13 builds.  Instead,
> someone would have to be willing to cherry pick the patches into the
> Debian build files for 3.5.13, and remove any renaming that has already
> been completed.
> To summarize, in principle I would love to see SRUs for the main supported
> distributions.  In practice we need more manpower to see it happen. ;-)
> Tim

Yes, now I understand why there will be no upgrade to 3.5.13.

But it seems it's not a comfortable situation for TDE, it's a circle:
without resource$ that leads to manpower, Trinity does progress very
slow, BUT if it progresses slow, large corporations or else that can
sponsor TDE development will run away.

May I gave a suggestion?

Why not make a release, 3.5.14, in early January, after the move to
Git and the rename thing is completed??
Even if it cures only a small bunch of bugs, it will be good, in many respects.

I don't know about others, but for myself, I can wait till January,
but I will not wait for six months to have some needed polishing done,
and will go away from TDE.

What you think?