Skip to content

prepare 3.5.3 release #122

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

Merged
merged 105 commits into from
Apr 26, 2019
Merged

prepare 3.5.3 release #122

merged 105 commits into from
Apr 26, 2019

Conversation

eli-darkly
Copy link
Contributor

[3.5.3] - 2019-04-26

Fixed:

  • Segment rollout calculations did not work correctly if the rollout was based on a user attribute other than key; all users would end up in the same bucket. (Thanks, m6w6!)
  • Running the SDK unit tests is now simpler, as the database integrations can be skipped. See CONTRIBUTING.md.

Note on future releases

The LaunchDarkly SDK repositories are being renamed for consistency. This repository is now php-server-sdk rather than php-client.

The package name will also change. In the 3.5.3 release, it is still launchdarkly/launchdarkly-php; in all future releases, it will be launchdarkly/server-sdk. No further updates to the launchdarkly/launchdarkly-php package will be published after this release.

eli-darkly and others added 30 commits July 16, 2018 16:05
add new version of allFlags() that captures more metadata
add ability to filter for client-side flags only
implement evaluation with explanations
# Conflicts:
#	src/LaunchDarkly/LDClient.php
add option to reduce front-end metadata for untracked flags
eli-darkly and others added 23 commits January 25, 2019 17:05
simplify & move feature requester/event publisher code
* add step to wait on Consul
…ttrs

coerce user attributes to strings when necessary, don't send events without valid users
add release script (version update only)
add param to skip db tests, update docs for new repo name
…ests

add tests for rollout calculations, + misc test cleanup
@eli-darkly eli-darkly requested a review from bwoskow-ld April 26, 2019 03:50
CONTRIBUTING.md Outdated
@@ -1,4 +1,37 @@
Contributing to the LaunchDarkly SDK for PHP
================================================
# Contributing to the LaunchDarkly SDK FOR PHP
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

FOR should be for

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also, the title should have "Server-side" in it.

CONTRIBUTING.md Outdated
## Submitting bug reports and feature requests

The LaunchDarkly SDK team monitors the issue tracker associated with the `launchdarkly/php-server-sdk` SDK repository. Bug reports and feature requests specific to this SDK should be filed in this issue tracker. The SDK team will respond to all newly filed issues within two business days.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In my other pull requests I linked to the issue tracker and then just said "... with the SDK repository" since the link made it clear to which SDK repository I was referring. It would be good to include a link here too.

Example: https://github.com/launchdarkly/go-server-sdk-private/pull/141/files#diff-6a3371457528722a734f3c51d9238c13R9


require 'vendor/autoload.php';
Refer to the [SDK reference guide](https://docs.launchdarkly.com/docs/php-sdk-reference) for instructions on getting started with using the SDK.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

4 participants