On Tuesday 17 January 2012 05:29:33 pm Darrell Anderson wrote:
> Article:
>
> http://www.datamation.com/open-source/the-fragmentation-of-the-linux-deskto
>p-1.html
>
> End of the first page:
>
> "...Because maintaining and updating the code is a huge effort, and the
> development team is small, TDE does suffer from more bugs than you may be
> used to...."
>
> Our release date goal is May 2012, but let's not release R14.0.0 unless all
> significant blocker, critical, and major bugs are resolved. :)
>
> I would like to ask that we consider point releases when serious bugs need
> to be backported to a current release. For example, when we need to release
> R14.0.1 then we build and release new packages. I don't think any of us
> have been doing that.
>
> Just thinking out loud....
>
> Darrell
>

Just replying out loud.....

I can see that some of the comment from datamation maybe is waranted.

For me the fustration is building a package from git repo say tdebase on a 
monday then working on several other packages and then update the local git 
repo rebuilding tdebase on friday results in tdebase not building at all.  
Possibility due to a commit/patch/update in the source.  I have since 
abandoned building from git and only use the 3.5.13 tarballs which have 
worked well for me.

My question is before a commit is made does whoever 
changed/updated/patched/crunched/mutilated the code, first see if it builds 
without barfing/puking then do the commit?

As for running TDE in general (which I have run it exclusive since I finished 
the arch linux build scripts last month) I have not experienced any breakage 
etc except for a few things in some of the apps that are minor and I can wait 
them until someone gets to fixing them so I don't see any big problema with 
running TDE.

salamat po