Skip to content

Commit

Permalink
Release 25.0.0.
Browse files Browse the repository at this point in the history
  • Loading branch information
vtsao committed Dec 22, 2016
1 parent 7abdf85 commit 5eea2f7
Show file tree
Hide file tree
Showing 3,526 changed files with 165,348 additions and 1,746,314 deletions.
The diff you're trying to view is too large. We only load the first 3000 changed files.
120 changes: 120 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,120 @@
### 25.0.0

##### AdWords

* Added support and examples for v201609.
* Removed support and examples for v201607.
* Fixed
[issue #168](https://github.com/googleads/googleads-php-lib/issues/168).
* Fixed [issue #175](https://github.com/googleads/googleads-php-lib/pull/175).
* Fixed [issue #181](https://github.com/googleads/googleads-php-lib/pull/181).
* Refactored how to specify what format a report is downloaded in
`ReportDownloader` by introducing `ReportDownloadResult`.
* Added support for including utility usage in the user agent header.

##### DFP

* Added support and examples for v201611.
* Removed support and examples for v201608.
* Renamed `DateTimeUtils` to `DfpDateTimes` and refactored some of its methods
to make it easier to understand and use.

##### Common

* Library is now stable and no longer in beta. See the
[Upgrading guide](https://github.com/googleads/googleads-php-lib/blob/master/UPGRADING.md)
for details on how to upgrade.
* Fixed the issue that some enum values whose names conflict with PHP reserved
keywords were generated by prepending "a", e.g., "aDEFAULT". They are now
generated by appending "VALUE", e.g., "DEFAULT_VALUE".
* Removed `__default` const from all generated pseudo-enum classes as it's not
necessary.
* Fixed
[issue #173](https://github.com/googleads/googleads-php-lib/issues/173).
* Refactored logging to support logging to different channels. There is now a
SOAP logger, as well as other product-specific loggers.
* Added convenience config options for core AdWords and DFP loggers to setup
logging to a specified file.
* Fixed [issue #187](https://github.com/googleads/googleads-php-lib/pull/187).
* Relaxed all library dependencies to use ^ instead of ~.
* Various internal utility refactoring to make utilities clearer in what they
do and easier to understand.

### 1.4.0-beta

##### AdWords

* Added support and examples for v201607.
* Removed support and examples for v201605.
* User agent is now optional. If no user agent is specified, 'unknown' will be
passed instead. If provided, user agent must contain US-ASCII characters
only.
* Added BatchJobs to support batch processing using BatchJobService
([issue #145](https://github.com/googleads/googleads-php-lib/issues/145)).
* Added some examples for v201607.

##### DFP

* Added support and examples for v201608.
* Removed support and examples for v201602.

### 1.3.1-beta

##### DFP

* Added v201602 retrieval examples.

##### Common

* Fixed
[issue #143](https://github.com/googleads/googleads-php-lib/issues/143) and
[issue #144](https://github.com/googleads/googleads-php-lib/issues/144).

### 1.3.0-beta

##### AdWords

* Added report downloader utility.
* Added support and examples for v201605.
* Removed support and examples for v201603.
* Added support for reporting request header
[`useRawEnumValues`](https://developers.google.com/adwords/api/docs/guides/reporting#request-headers).

### 1.2.0-beta

##### Common

* Added a GetRefreshToken.php example that helps you generate an OAuth2
offline refresh token for installed application flows.

### 1.1.0-beta

##### AdWords

* Added support for v201603.
* Removed support for v201601.

##### DFP

* Added support for v201602.
* Removed support for v201511.
* The report downloader utility now uses Guzzle, instead of Curl, to make HTTP
requests.

##### Common

* OAuth2 is now handled by the [Google PHP Auth
Library](https://github.com/google/google-auth-library-php).
* [OAuth2 service
accounts](https://developers.google.com/identity/protocols/OAuth2ServiceAccount)
are now supported and JSON key credentials can be loaded from the
adsapi_php.ini file.
* SSL peer verification is now enabled by default for SOAP requests.
* Instances of ApiException are now thrown from services if there was a SOAP
fault, instead of PHP's generic SoapFault.

### 1.0.0-beta

##### Common

* Initial release.
55 changes: 36 additions & 19 deletions CONTRIBUTING.md
Original file line number Diff line number Diff line change
@@ -1,29 +1,46 @@
# Contributor License Agreements
## Contributor License Agreements

We'd love to accept your code patches! However, before we can take them, we have to clear a couple of legal hurdles.
We'd love to accept your code patches! However, before we can take them, we have
to clear a couple of legal hurdles.

- Please fill out either the individual or corporate Contributor License Agreement.
- If you are an individual writing original source code and are sure you own the intellectual property, then you'll need to sign an individual CLA available at:
* Please fill out either the individual or corporate Contributor License
Agreement.

https://developers.google.com/open-source/cla/individual.
* If you are an individual writing original source code and are sure you
own the intellectual property, then you'll need to sign an individual
CLA available at:

- If you work for a company that wants to allow you to contribute your work to this client library, then you'll need to sign a corporate CLA available at:
https://developers.google.com/open-source/cla/individual

https://developers.google.com/open-source/cla/corporate.
* If you work for a company that wants to allow you to contribute your
work to this client library, then you'll need to sign a corporate CLA
available at:

Follow either of the two links above to access the appropriate CLA and instructions on how to sign and return it. Once we receive the CLA, we'll add you to the official list of contributors and will be able to accept your patches.
https://developers.google.com/open-source/cla/corporate

# Submitting Patches
Follow either of the two links above to access the appropriate CLA and
instructions on how to sign and return it. Once we receive the CLA, we'll add
you to the official list of contributors and will be able to accept your
patches.

- Sign a Contributor License Agreement (see above).
- Join the appropriate product discussion forum.
- AdWords API: https://developers.google.com/adwords/api/community/
- DFP API: https://developers.google.com/doubleclick-publishers/community
- DFA API: https://developers.google.com/doubleclick-advertisers/reporting/community
- Create an issue on the library issue tracker if there isn't one already. Use this issue to co-ordinate the changes with the library maintainer.
- Fork the library, make the changes and send a [pull request](https://help.github.com/articles/using-pull-requests).
- The library maintainer will work with you to review and apply the patch.
## Submitting Patches

# If you can't become a contributor
* Sign a Contributor License Agreement (see above).
* Join the appropriate product discussion forum.
* AdWords API: https://developers.google.com/adwords/api/community/
* DFP API: https://developers.google.com/doubleclick-publishers/community
* DFA API:
https://developers.google.com/doubleclick-advertisers/reporting/community
* Create an issue on the library issue tracker if there isn't one already. Use
this issue to co-ordinate the changes with the library maintainer.
* Fork the library, make the changes and send a [pull
request](https://help.github.com/articles/using-pull-requests).
* The library maintainer will work with you to review and apply the patch.

If you can't become a contributor, but wish to share some code that illustrates an issue / shows how an issue may be fixed, then you can attach your changes on the issue tracker. We will use this code to troubleshoot the issue and fix it, but will not use this code in the library unless the steps to submit patches are done.
## If you can't become a contributor

If you can't become a contributor, but wish to share some code that illustrates
an issue / shows how an issue may be fixed, then you can attach your changes on
the issue tracker. We will use this code to troubleshoot the issue and fix it,
but will not use this code in the library unless the steps to submit patches are
done.
Loading

0 comments on commit 5eea2f7

Please sign in to comment.