Every project has to kick off somewhere.  Yep well that's a no brainer.  However, the number of projects that I've seen where the planning step has been omitted is too high.  A throughly planned out project with as many features scoped before you start coding is critical in completing a project.  Whilst projects and their requirements are always fluid, the initial critical scoping is so important. Fail to plan, planning to fail There is no one way to plan.  Yes I've seen...

As a process I apply patches locally first, then using git upload the update(s) to a development site on the server.  Once the testing has been completed, the final step to apply the patch to the production site.   Using Terminal or your preferred shell program, navigate to the correct directory.  Then run this command using the name of the patch file (example.patch): patch < example.patchHowever, if you are patching Drupal core then remember to patch from the root directory...