April 03, 2012
by James Creasy, Director of Product Technology, Perforce SoftwarePosted In:
March 30, 2012
Continuous integration and Agile development are two distinct but related trends in software development. Continuous integration (CI) is really about increasing transparency, but usually manifests itself as automated build and test routines. To put it very briefly, building and testing early and often is a great way to make sure that you’re actually building what you wanted to, and expose potential problems early on.
March 28, 2012
by Bill White
I think everyone understands that QA is the organization responsible for testing our software. We're also responsible for reporting on the results of that testing, i.e., providing an assessment of product quality based on the number and nature of the defects that we uncover prior to release and that emerge later as customers use our products in new and unexpected ways.
March 26, 2012
Perforce streams let you capture important information about what actually goes into a codeline. Using stream paths, you can select active modules (modules that are branched and worked on), import other modules as read-only dependencies from the parent stream, and so on. (For more information on stream paths, read this post by Laura Wingerd.)
March 22, 2012
While I don’t normally find press releases very interesting, our friends at BigLever Software, a Perforce integration partner, created a very interesting way to picture the complexity of modern development projects. (BigLever’s CEO, Dr. Charles Krueger, also contributed a guest blog article on systems and software asset sharing.)
March 20, 2012
by James Creasy, Director of Product Technology, Perforce Software
If you can pardon the hyperbolic headline, I’ll explain how Perforce came to submit a few patches to the Git open source project and what our future plans are.