The more the maintenance and building process is automated, the easier it is to make releases.

Well, that assumes I want to merge the changes in the first place. And that there are any changes to merge.

My remark applies to software projects at large

I already sent you a patch to dasm-tigcc on 20080525, but you don't want it

What about "TI-68k Developer Utilities" ? That would emphasize that these are "companion tools" to the main development tools that the rest of the TIGCC/GCC4TI toolchain is.

That sounds good.

ACK.
ttdasm used to be part of these utilities. Do you have a valid gripe against GCC4TI importing some form of dasm-tigcc (which is FLOSS, and just better than ttdasm both from a functionality and legal POV) in its repository, in order to replace ttdasm ?