Re: Release of RosAsm V.2.025a

The only sad thing on your statements Randall is that you are the one
who don=B4t know what you are talking about, and, by consequence, you
are spreading lies again.

Example:

"And resolving things like conflicting names, merging duplicate code,
and all those other things that plague this type of "monolithic"
software development. The really sad thing is that the RosAsm team
really doesn't know any better. "

Just a lie .. Duplicated symbols or functions when merged the user is
warned because it won =B4t assemble the file due to the duplications.
The error management is exactlyto prevent this sort of things.


"> > Do you have to wait somebody has finished working to begin
modifying the project?

> Our rule is quite simple: Once a volunteer has been attributed a TITLE,
_=
he_, and only _he_ is allowed to touch _his_ TITLE.

See the statement above.
Yep. The RosAsm scheme truly sup****ts team projects :-) :-) :-)

> In other words, we never have two volunteers writing the same TITLE at
th=
e same time,

The RosAsm team doesnt understand what a "team project" is all about. "

Maybe you didn=B4t read what i posted or you just disconsidered on your
attacks on rene...but..on all you posted you really seems clueless on
what it is all about, the clip features, the incinclude statements
preparsers and the lib scanners.

"They *really, really* don't understand how team project management
should be done."

So, pls enlight us with your "universal" knowledge.

If that means disseminating arrogancy or flames on our team of
co-workers...Sorry..this won=B4t happen :)

A team work using different files and people thinking together of the
whole project is what a team work is based on. The way it is developed
is not different from other techniques of working in team you want to
impose...



Best Regards,
Guga