+3
I have worked in midrange shops where where we could only build from a
CMS library. You could "local compile" a single source file within LSE
or a BUILD-ONE command file, but you could only build a testable binary
from a CMS library. Every developer had their own CMS (Code Management
System). Once we had local compiled the files we changed we had to put
them back into CMS to build a testable binary. When we thought things
worked we had to promote to one of the integration testing CMS areas
T01-T99.
Whenever we started a new project we nuked our CMS and took a fresh pull
from Production P01.
The pain of checking in all changes before testing is paid for by not
having to spend days tracking something like this down.
On 2/15/20 5:00 AM, interest-requ...@qt-project.org wrote:
On 07/02/2020 21.37, Jonathan Purol wrote:
After manually removing every line of code to see when a MVCE would
work, I found a loose `blockSignals(true)` flying around that was there
from a debugging session.
`git diff`? Stuff like this is why you should use a VCS (it doesn't have
to be git) even for personal projects, and commit early and often, so
that when you're working on something, it's easy to see what's changed.
</PSA>
--
Roland Hughes, President
Logikal Solutions
(630)-205-1593
http://www.theminimumyouneedtoknow.com
http://www.infiniteexposure.net
http://www.johnsmith-book.com
http://www.logikalblog.com
http://www.interestingauthors.com/blog
_______________________________________________
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest
