Phings v160526

• Adding support for project_required_os in #98
• Adding support for project_php_required_bits in #98
• Adding support for project_php_required_extensions in #98
• Support for %now in version strings.
  • Suggested use: project_version = %y%m%d.%now
  • %now = time() % 86400 ... See also: http://semver.org/
  • e.g., 160525.49351, where .49351 is a minor version represented by the current number of seconds into the current day. Using versions like this in our build process can make it easier to maintain projects that are commonly updated more than once each day; e.g., the WPSC.
• Noting that $ phing release depends on a PEAR extension.
  • $ pear install VersionControl_Git-0.4.4; on a Mac.
  • I removed calls that relied on this extension, in favor of <exec command="git ....
• Resolved issue in #90 & resolved issue in #88 (however, see note below).
• Fix bug that prevents namespace updates (sometimes) in core rebranding via composer install.
• Adding support for a new CLI switch: $ phing release -D interactive=true. The interactive flag is off by default now, so that it's not necessary to answer prompts. If you want to take extra care during a release you can enter interactive mode where you are given a choice before things occur; e.g., prompted to commit and push changes in lite repo variation. However, I consider this interactive mode to be deprecated now; i.e., that's why it's off by default now. The next checklist items covers some of the new $ phing release functionality. Given the new functionality, it's not expected that an operator would need to answer prompts during an automated release process.
• Optimize autoloader built by Composer.
• Teach the Phing system how to do GitHub releases following our Git workflow standards. See also: https://github.com/websharks/phings/wiki/GitHub-Releases