Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enhance Composer Integration and More #100

Merged
merged 34 commits into from
May 26, 2016
Merged

Enhance Composer Integration and More #100

merged 34 commits into from
May 26, 2016

Conversation

jaswrks
Copy link
Contributor

@jaswrks jaswrks commented May 25, 2016

  • 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 Improve Composer require-dev During Build #90 & resolved issue in Improve Composer dependency handling in Lite build #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.

#88 has been resolved in this branch. However, in order for this issue to go away in existing repos there is an action required. In Comet Cache Pro's composer.json file we have this:

"require": {
    "php": ">=5.4",
    "websharks/wp-php-rv": "160504",
    "websharks/html-compressor": "160118",
    "websharks/sharkicons": "160221"
  },

After that section, we need to add a new section that is specifically for the lite variation.

"require-lite": {
    "php": ">=5.4",
    "websharks/wp-php-rv": "160504",
    "websharks/sharkicons": "160221"
  },

raamdev added a commit to wpsharks/comet-cache-pro that referenced this pull request May 25, 2016
@jaswrks
Copy link
Contributor Author

jaswrks commented May 26, 2016

Automated GitHub releases via Phing. See: https://github.com/websharks/phings/wiki/GitHub-Releases

@jaswrks jaswrks merged commit 10a73ca into 000000-dev May 26, 2016
@jaswrks jaswrks deleted the feature/enhance branch May 26, 2016 12:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant