Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>Your workflow can be improved, here is a list of my advice:</p> <ul> <li>Start using SVN branches and release builds/deployments on a regular cycle. </li> <li>Figure out how long your deployment cycle should be, leaving time in for QA. So for instance if you are going to release a build every month have 3 weeks of development and 1 week of QA. Freeze development for that build after 3 weeks except for bug fixes. </li> <li>Decide on a numbering scheme for your builds that allows room to grow</li> <li>Utilize a ticketing system (ActiveCollab, JIRA, Mantis ... etc) and enforce the rule that any commit has to be associated with a ticket. Pick one where you can make your commits show up automatically in the ticket. </li> <li>If you are going to start to document your requirements before starting development, don't gather your requirements in the ticketing system (for gods sake)</li> <li>Doing this will help you determine what features are in a given build. So make some sort of release notes with a list of the ticket numbers or a general description of the tickets for each build. </li> <li>Embed your build numbers in your application so that you can track deployments on any given system. </li> <li>Start working with automated testing tools PHPUnit for unit tests and Selenium for Functional tests to speed up QA and increase the quality/stability of the web application by decreasing the likelihood that day to day changes introduce new bugs.</li> <li>Hudson and Phing can be lifesavers for automating your builds and automating your Testing. </li> </ul>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload