>Aegis doesn't guarantee no bugs. It simply requires a new test for
>every change and re-runs all the old tests, as well as the new test, on
>the submitted new code before it can become the baseline.
>
>If the rest of your process is "working" then no bugs will ever be
>re-introduced. If the change is a bug fix then the one more bug will be
>squashed and it can never be re-introduced either.
Then I fail to see how, as you implied, Aegis will _prevent_ bug fix branches.
>> This is one way to do it. Some would use a version control tool.
>
>I AM USING A VERSION CONTROL TOOL! I'm just using it one step removed
>by putting the configuration specification into a "script" that's
>version controlled!
OK, so you are. I think I see now. You have one line of development for each
of your binary files (possibly hundreds if you're developing a web site). Each
version of your install scripts know exactly which version of which binary files
it needs. It sounds pretty messy to me.
Noel
This communication is for informational purposes only. It is not intended as
an offer or solicitation for the purchase or sale of any financial instrument
or as an official confirmation of any transaction. All market prices, data
and other information are not warranted as to completeness or accuracy and
are subject to change without notice. Any comments or statements made herein
do not necessarily reflect those of J.P. Morgan Chase & Co., its
subsidiaries and affiliates.
_______________________________________________
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
