Skip to content

Commit 9a5528c

Browse files
committed
(no issue) update release notes for build issues.
1 parent 9009564 commit 9a5528c

File tree

1 file changed

+8
-6
lines changed

1 file changed

+8
-6
lines changed

RELEASE_NOTES.md

Lines changed: 8 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ These notes apply to v2.2rc2 of 2017-06-26.
66

77
[#52](https://github.com/adobe-apiplatform/user-sync.py/issues/52): This release runs on both Python 2 and Python 3 (2.7, 3.4, 3.5, and 3.6 to be precise)!
88

9-
[#182](https://github.com/adobe-apiplatform/user-sync.py/issues/182): At long last, you can select users in nested groups. The new implementation also allows us to avoid fetching the entire directory when the users are only supposed to come from specific groups, as with `--users mapped` ([#129](https://github.com/adobe-apiplatform/user-sync.py/issues/129)). There is a new LDAP setting `group_member_filter_format` which controls how users are selected for groups (default is the backward-compatible immediate members only).
9+
[#182](https://github.com/adobe-apiplatform/user-sync.py/issues/182): At long last, you can select users in nested groups. The new implementation for determining group members also allows us to avoid fetching the entire directory when the users are only supposed to come from specific groups, as with `--users mapped` ([#129](https://github.com/adobe-apiplatform/user-sync.py/issues/129)). There is a new LDAP configuration setting `group_member_filter_format` which controls how users are selected for groups (default is "immediate members only", which is backward compatible with prior releases).
1010

1111
[#236](https://github.com/adobe-apiplatform/user-sync.py/issues/236): Directory users can now be pushed directly to Adobe, rather than synchronized with a fetch of Adobe users. A new command-line argument `--strategy push` (as opposed to the default `--strategy sync`) controls this.
1212

@@ -16,22 +16,24 @@ These notes apply to v2.2rc2 of 2017-06-26.
1616

1717
## Bug Fixes
1818

19-
[#227](https://github.com/adobe-apiplatform/user-sync.py/issues/227): crashes due to bad user keys.
19+
[#227](https://github.com/adobe-apiplatform/user-sync.py/issues/227): Fixed crashes due to bad user keys.
2020

21-
[#233](https://github.com/adobe-apiplatform/user-sync.py/issues/233): exceptions in LDAP connections are handled gracefully, as are keyboard interrupts.
21+
[#233](https://github.com/adobe-apiplatform/user-sync.py/issues/233): Exceptions in LDAP connections are handled gracefully, as are keyboard interrupts.
2222

23-
[#235](https://github.com/adobe-apiplatform/user-sync.py/issues/235): crash if Adobe ID user has no username or domain info.
23+
[#235](https://github.com/adobe-apiplatform/user-sync.py/issues/235): Fixed a crash that occurred if an Adobe ID user had no username or domain info.
2424

2525
[#240](https://github.com/adobe-apiplatform/user-sync.py/issues/240): When using the LDAP connector, the domain of each user is now correctly defaulted to the email domain.
2626

27-
[#244](https://github.com/adobe-apiplatform/user-sync.py/issues/244): The build instructions are now provided for all platforms, and the default `Makefile` allows for the use of pre-compiled, platform-specific wheels.
27+
[#244](https://github.com/adobe-apiplatform/user-sync.py/issues/244): Build instructions are now provided for all platforms, and the default `Makefile` allows for the use of pre-compiled, platform-specific wheels.
2828

2929
[#247](https://github.com/adobe-apiplatform/user-sync.py/issues/247): There is no more use of the `uid` attribute in LDAP directories.
3030

3131
## Compatibility with Prior Versions
3232

33-
This version is fully backwards-compatible with version 2.1.1. As mentioned above, there are new configuration settings for controlling network behavior and update strategy.
33+
This version is fully backwards-compatible with version 2.1.1. As mentioned above, there are new configuration settings for filtering group members and controlling network behavior, and there is a new command-line option for controlling the update strategy. See [the docs](https://adobe-apiplatform.github.io/user-sync.py) for full details about configuration.
3434

3535
## Known Issues
3636

37+
Because the releases on Windows are built with pre-compiled dependencies, we have to lock down the versions of pycryptodome and PyYAML used in each release. Thus they may not always be the latest version (as, for example, with this release, which uses pycryptodome 2.4.35.1 rather than 2.4.36).
38+
3739
On the Win64 platform, there are very long pathnames embedded in the released build artifact `user-sync.pex`, which will cause problems unless you are on Windows 10 and are either running Python 3.6 or have enabled long pathnames system-wide (as described in this [Microsoft Dev Center article](https://msdn.microsoft.com/en-us/library/windows/desktop/aa365247(v=vs.85).aspx)). To work around this issue on older platforms, set the `PEX_ROOT` environment variable (as described [in the docs here](https://adobe-apiplatform.github.io/user-sync.py/en/user-manual/setup_and_installation.html)) to be a very short path (e.g., `set PEX_ROOT=C:\pex`).

0 commit comments

Comments
 (0)