Slashdot Mirror

The stretching FAQ is a very good resource: http://www.cmcrossroads.com/bradapp/docs/rec/stretching/

Stretching while your muscles are cold is a very bad idea. One of the things that confuses people is how crazily flexible your body is when you are young. You can usually do just about any stupid ass thing and you will not get seriously injured. But as you get older, you lose it. Warm up is essential. Stretching before exercise (before you are warm) is an invitation to injury.

But extrapolating from that to assume that stretching is a bad idea is wrong. Flexibility is extremely useful. If you don't move your body through it's full range of motion, you will gradually lose the ability to do so. Then you are not only at risk of injury during exercise, but also in every day life. Because the loss of flexibility is so gradual, many people don't realize it. But before you know it, it's gone and then you lose your ability to move.

Stretching isn't something you chuck in at the beginning of a workout. It is part of a workout (or even the workout itself). You have to treat it seriously and understand how to do it properly. Just like anything else.

We manage just fine. If it's too complicated for you to understand then just pretend the magic file fairies do the work. Of course there are times different people change the same section of a file in which case whomever was last gets to play the part of magic file fairy.

Person A is prevented from dicking around at random because they'd like to stay employed.

The merging is done with something along the lines of: http://www.cmcrossroads.com/articles/cm-journal/a- trustworthy-3%11way-merge.html (warning: advertisement disguised as article)

PARSEARGS
 
                        extracted from Eric Allman's
 
                            NIFTY UTILITY LIBRARY
 
                          Created by Eric P. Allman
                            <eric@Berkeley.EDU>
 
                        Modified by Peter da Silva
                            <peter@Ferranti.COM>
 
                  Modified and Rewritten by Brad Appleton
                          <brad@SSD.CSD.Harris.COM>

PARSEARGS
 
                        extracted from Eric Allman's
 
                            NIFTY UTILITY LIBRARY
 
                          Created by Eric P. Allman
                            <eric@Berkeley.EDU>
 
                        Modified by Peter da Silva
                            <peter@Ferranti.COM>
 
                  Modified and Rewritten by Brad Appleton
                          <brad@SSD.CSD.Harris.COM>

This is why many companies start a Production Services team. Generally this means the hiring of a Build and Release Engineer or Manager who has an IT background and an understanding of Software Development.

The alignment of the Production team varies. At some companies they report to the development organization (e.g. to the Manager or Director of Software Engineering) and at other companies they report to Quality Assurance.

I would suggest that you check out the site: http://cmcrossroads.com/

http://www.cmcrossroads.com/ Everything you would want to ask.

"The better SCM initiative was established to encourage improved OSS/FS SCM systems, by discussing and comparing them. Among other things, see their comparison file. Zooko has written a short review of OSS/FS SCM tools. Shlomi Fish's OnLamp.com article compares various CM systems as does his Evolution of a Revision Control User. The arch folks have developed a comparison of arch with Subversion and CVS (obviously, they like arch). Another pro-arch discussion is Why the Future is Distributed. A pro-subversion discussion is available at Dispelling Subversion FUD. Slashdot had a discussion when Subversion 1.0 was announced. Kernel traffic posted a summary of a technical discussion about BitKeeper. Brad Appleton has collected lots of interesting SCM links. jemfinch has some interesting essays about SCMs (he uses the term VCS), including why he thinks the approach to branches used by Darcs, Arch, and Bazaar-ng is a poor one. A brief overview of SCM systems that can run on Linux is available."

There are lots of OSS/FS software configuration management (SCM) tools. CVS, Subversion (SVN), and GNU arch get lots of press, but there are many others such as Aegis, CVSNT, Darcs, FastCST, OpenCM, Vesta, Codeville, Bazaar and Bazaar-NG.

You might also take a peek at my paper Software Configuration Management (SCM) Security.

IMHO there are much better alternatives out there. I use Subversion at home and Perforce (definitely worth the cost) at work and I'll never go back. Source control without atomic commits really isn't much control at all...

ClearCase is not a VCS... it's a CMS...

read all about them here