#1051000 (Bug #78647) ** On an Edge Server with submit.unlocklocked=1, a submit which fails with "Out of date files must be resolved or reverted" could incorrectly alter the resolve state of the open files if the conflicting change was submitted simultaneously.
#1047834 (Bug #78444) ** The replica-specific table db.user.rp is now journaled. This means that the table data will appear in checkpoints, journals and dumps. The replica pull thread automatically filters out all db.user.rp records from its P4TARGET server, which is normally the desired behavior, since records in this table are unique to each replica's activity. However, for maintaining warm standby replicas of other replicas, you can set rpl.replay.userrp=1 for the standby replica to disable the filtering and replicate db.user.rp data.
#1046060 (Bug #73967) ** 'p4 -ztag servers' could report incorrect values for the 'User' field for server specs upgraded from an older release.
#1045565 (Bug #78497) ** Promoting a shelf, then subsequently deleting it, using the same network connection to the Edge Server could fail to properly delete the shelf.
#1042871 (Bug #78427) * 'p4 -P <ticket> sync --parallel' will no longer give authentication errors for the file transfer sub-processes.
#1040963 (Bug #78416) ** The new command 'p4 switch' was incorrectly forwarding when executed from an edge server.
#1039853 (Bugs #73075, #74961) ** The revision specifier @client was not working properly for clients bound to a build-server.
#1039277 (Bug #78383) ** A 'p4 describe' command which accesses a remote promoted shelf now properly reports any communications-related error conditions which occur when retrieving the remote shelf.
#1039178 (Bug #77617) ** 'p4 resubmit' can now resubmit an unsubmitted change which involved the oldest non-purged revision of a file of type +S.
#1037755 (Bug #76982) * If a 'p4 sync --parallel' child process encounters an error writing files to the local machine, the parent 'p4 sync' command now returns a non-zero exit status to the operating system.
#1037486 (Bug #76283) ** Performance of 'p4d -z -jv <file>' is substantially improved.
#1036596 (Bug #77433) ** In a distributed configuration, 'p4 unshelve' no longer takes the global exclusive file lock for a file of type +l which is unshelved for add.
#1036485 (Bug #77069) ** A 'p4 describe -S' command on an Edge Server which specified more than 1 promoted shelf which was created on a different Edge Server would fail with an 'Unknown changelist' message.
#1036167 (Bug #76002) ** Stream 'import+' paths are not being referenced when the stream type is virtual. This was causing warnings on 'p4 edit' and a failure on 'p4 submit' of any files within these import+ paths. Fixed.
#1035768 (Bug #78164) ** In a distributed environment, the change-failed trigger now runs on the commit server rather than on the edge server.
#1035121 (Bug #78036) ** The 'p4 attribute' command is not allowed on a server which was created by 'p4 init'; also, when a revision is copied to another server by the 'p4 fetch', 'p4 push', or 'p4 unzip' commands, its traitLot field is automatically cleared in the destination.
#1033960 (Bug #78106) ** In a distributed environment (edge/commit) promoting of shelves to the commit server could result in a long duration lock being held over multiple commands. This would be more visible when using P4V rather than the command line.
#1033794 (Bug #75637) ** 'p4 help administration' now lists the three LDAP related commands: 'p4 ldap', 'p4 ldaps' and 'p4 ldapsync'.
#1032558 (Bug #78084) ** 'p4 push -n -v' and 'p4 fetch -n -v' no longer report that changelists to be pushed/fetched would be renumbered as change #0.
#1033412 (Bug #78198) * ** *** Updated version of OpenSSL to 1.0.1m to address possible vulnerabilities: CVE-2015-0287, CVE-2015-0293, and CVE-2015-0288.
#1032557 (Bug #76351) Performance problems in a distributed environment exhibited by 'p4 submit' and 'p4 shelve -p' introduced by change 969974 is addressed. Specifically, file transfer time was degraded under conditions of high latency when submitting or promoting changes with many files. This problem that was introduced in the initial 2015.1 release has been fixed.
#1032042 (Bug #74056) ** 'p4 sync --parallel' would fail to expand RCS keywords properly.
#1031202 (Bug #76013) ** 'p4d -xx db.working db.have' could create spurious delete records for db.working if a file opened for move or delete is subsequently moved and submitted by another client and the opened file is then synced to the head revision.
#1030772 (Bug #77871) ** 'p4 -ztag pull -l -s' now provides tagged output.
#1030698 (Bug #77559) ** A build-server replica would incorrectly process the View: field for labels, causing the wrong set of revisions to be specified by the label.
#1030610 (Bug #77873) ** 'p4 protects -u' for a service/operator user was showing protects access to content, although service/operator users cannot be used to browse or update a repository.
#1030042 (Bug #77728) ** The 'min' argument of the '--parallel' options is now correctly enforced when submitting through an edge server.
#1029907 (Bug #78113) ** 'p4 switch' and 'p4 switch -l' were taking out an unnecessary client lock.
#1029218 (Bug #78099) ** 'p4 fetch' and 'p4 push' no longer cause an "unknown command" error when the remote server is a DCS node.
#1028633 (Bug #77558) ** A replica with lbr.replication=cache was not able to access labels using the autoreload option.
#1028018 (Bug #78012) Performance problems in a distributed environment exhibited by 'p4 submit' and 'p4 shelve -p' introduced by change 969974 is addressed. Specifically, file transfer time was degraded under conditions of high latency when submitting or promoting changes with many files. This problem that was introduced in the initial 2015.1 release has been fixed.
#1027765 (Bug #77595) ** 'p4 export -f' now formats the domain type column correctly for unloaded clients, unloaded labels, and unloaded task streams.
#1026750 (Bug #77504) ** * 'p4 -Zproxyload sync --parallel=...' now correctly updates the proxy's archive cache without sending files to the client.
#1026544 (Bug #77280) ** If a change submitted via an Edge Server was rejected by a change-submit or change-content trigger on the Commit Server, the change's files were modified to read-only mode on the client machine rather than being left in writable mode.
#1026312 (Bug #77435) ** A 'p4 integ' or 'p4 unshelve' command on an Edge Server which failed to open a +l file due to a client-side file transfer error would leave an orphaned lock record in db.excl.
#1025869 (Bug #77886) ** A parsing problem with the 'p4d -i' flag is resolved. #1025589 (Bug #75647) ** 'p4 unload -c' from an edge server now allows unloading of clients with promoted shelves.
#1025619 (Bug #77726) ** 'p4 unsubmit' commands which have multiple arguments, and which terminate due to an error while processing an argument other than the first, now correctly sync the workspace with all the work that was successfully unsubmitted prior to that error.
#1025545 (Bugs #77656, #77672) ** Audit log records for the push, fetch, zip, and unzip commands, in both the structured audit log and the P4AUDIT log, now have improved precision and additional detail.
#1025484 (Bug #77626) ** The 'p4 unsubmit' and 'p4 resubmit' commands are not available on an Edge Server, and issuing them against an Edge Server now gives an error message.
#1025380 (Bug #77326) ** 'p4 zip' no longer creates an empty zip file if the specified fileset is empty.
#1024502 (Bug #77719) * The 'p4 init' or 'p4 clone' commands, when they connect to a shared server, would cause log records to be written as an "unknown" client program and "unknown" program version.
#1024419 (Bug #77730) ** The 'p4 ldapsync' could run on replicas, potentially changing the contents of the replica's db.group table. This change restricts 'p4 ldapsync' so that it may only run on the master; replicas may forward the command, if forwarding is enabled. If configured to run in the background on a replica, 'p4 ldapsync' will immediately stop.