Z-Push 2.6.x beta/pre-final updates
the release procedure for Z-Push 2.6.x versions will be the same as for Z-Push 2.5.x versions.
At latest in a couple of weeks pre-final branch will contain Z-Push 2.6.x releases. If for some reason you want to continue using Z-Push 2.5.x pre-final, you’ll have to disable the current Z-Push pre-final repository and checkout release/2.5 branch. More information about using branches is available at: https://wiki.z-hub.io/display/ZP/How+to+get+the+latest+Z-Push+code+from+GIT.
By using the pre-final repository you will automatically get fixes fast and install beta versions.
When a final is released, in the release/2.6 branch/pre-final repo this version also gets a tag, like version+1-beta0. So, 2.6.0 final in master is called 2.6.1.beta0 in release/2.6.
Changes are going to be continuously merged into the release/2.6 branch.
By using the pre-final repository you will get these changes when update/upgrade from the repository.
These changes will be part of the next released beta, but you will have them before the beta is officially released (a released beta is just a bundle of changes).
2.6.0 was released (final, in the GIT master branch)
in release/2.6 2.6.0 is called 2.6.1.beta0+0 (same thing, just a different name)
as changes are merged, the last number will increase, 2.6.1.beta0+6 are changes that are going to become 2.6.1.beta1. Same as 2.6.1.beta1+X are changes that are going to become 2.6.1.beta2 (or perhaps final if we consider these changes trivial enough that we don’t release another beta).
This thread is to keep you updated about the changes that are merged into the release/2.6 branch.
Alternatively you could get the same via a GIT checkout of the release/2.6 branch.
If you have any feedback about the version, please open a new thread mentioning the exact version number logged in your z-push log.
Z-Push pre-final repository now contains Z-Push 2.6.0 beta0+6. I’ll do another post for the official beta1 release, but if you want to check which issues were addressed, take a look here: https://jira.z-hub.io/projects/ZP/versions/11404 (JIRA account is required to view this page). Alternatively you can see the issues of this version at https://jira.z-hub.io/browse/ZP-1577?jql=project %3D ZP AND fixVersion %3D 2.6.0 ORDER BY priority DESC%2C updated DESC or on Z-Push roadmap page: https://wiki.z-hub.io/display/ZP/Roadmap#Roadmap-nextmajor.
WalterHof last edited by
I tried to follow the link, unfortunately I only get this error message:
**Sorry, you can’t view this page
This page is only available to Jira Software users. If you think you should be a Jira Software user, you should ask your administrator to give you application access to Jira Software.
Continue to project**
did you create a JIRA account on z-hub.io? The signup is open to everyone and that page doesn’t require any special permissions.
Alternatively you may filter the issues using fixVersion: https://jira.z-hub.io/browse/ZP-1577?jql=project %3D ZP AND fixVersion %3D 2.6.0 ORDER BY priority DESC%2C updated DESC
liverpoolfcfan last edited by
I’ve updated my previous post with a note that a JIRA account is required and provided alternative links to the issues.
Tickets in Z-Push 2.6.0 beta1:
[ZP-1451] - Description is empty.
[ZP-1530] - change charset for IMAP search
[ZP-1537] - Missing fields in GAB sync script
[ZP-1539] - Missing contacts in outlook GAB
[ZP-1541] - Add php-mbstring to Debian Buster packaging
[ZP-1545] - Always initialise content parameters in itemoperations
[ZP-1546] - Do not use return a bool value in GetMessage
[ZP-1548] - [gabsync] initialise variables with default values
[ZP-1552] - Description not stripped from private meeting in shared folder
[ZP-1557] - ArithmeticError: Bit shift by negative number
[ZP-1558] - Debian 10 package z-push-autodiscover missing php-xml dependency
[ZP-1561] - BackendIMAP: syncing existing messages does not download flag status
[ZP-1565] - BackendIMAP fix $Forwarded flag in SendMail()
[ZP-1572] - Attendees duplicated in Meetings
[ZP-1573] - [WARN] /usr/share/z-push/backend/kopano/kopano.php:2634 Uninitialized string offset
[ZP-1577] - BackendIMAP: Call to undefined function dbg_error_log using latest git
[ZP-1498] - Improve Caldav syncing of large calendar sets
[ZP-1513] - Check USE_CUSTOM_REMOTE_IP_HEADER for trusted proxies
[ZP-1518] - List currently available backend providers in config.php
[ZP-1521] - Add the option to disable KOE handling of setting a custom sync timeframe based on the total storesize
[ZP-1533] - Fixstates speedup
[ZP-1551] - Fixstates device driven
[ZP-1553] - use ldap uri instead of host and port for ldap_connect
[ZP-1554] - BackendSearchLDAP - fallback to displayname if lastname and firstname not set (if available)
[ZP-1555] - BackendIMAP detect iOS devices and set SYNC_BODYPREFERENCE_MIME accordingly
[ZP-1556] - PHP 7.4 Deprecated: Unparenthesized a ? b : c ? d : e in BackendIMAP and BackendCARDDAV
[ZP-1566] - Do not return free/busy information when querying groups
[ZP-1578] - Remove z-push-admin call in postinst
[ZP-1583] - Don’t expose Z-Push version
Tickets in Z-Push 2.6.1 beta 1:
[ZP-1584] - [autodiscover] Do not return 5XX code for unsupported schemas
[ZP-1586] - [gab2contacts] Deleted properties are not removed during sync
[ZP-1589] - iOS14 fills up “z-push-error.log”
[ZP-1590] - Wrong organiser email
[ZP-1593] - Invalid argument supplied for foreach
[ZP-1581] - BackendIMAP does not sync answered or forwarded state
[ZP-1582] - BackendIMAP use standardized “Importance” header (RFC4021) too
[ZP-1591] - Soft deletion of mails moved between folders
Tickets in Z-Push 2.6.2 beta 1:
[ZP-1600] - devicemanager.php:1004 Trying to access array offset on value of type bool
[ZP-1601] - IMAP_SMTP_METHOD smtp doesn’t work with self-signed certificates
[ZP-1602] - BackendCardDAV: invalid return type “false” in ChangesSink()
[ZP-1603] - Sending a meeting from a public calendar breaks Outlook sync
Tickets in 2.6.3 beta 1
[ZP-1624] - 1 year custom sync filter type support
[ZP-1599] - Read InstanceId in MeetingResponse
[ZP-1609] - Meetingrequest class doesn’t set commonstart and commonend properties
[ZP-1611] - Content-type usage in z_caldav.php is invalid
[ZP-1612] - Invalid return type of GetGALSearchResults() in BackendCardDAV and BackendSearchLDAP
[ZP-1617] - The iOS devices send two accept responses
[ZP-1625] - Link device to user for POST requests only
[ZP-1522] - Option to use local part for the login for caldav and carddav backends
[ZP-1621] - BackendCombined error in sprintf()
[ZP-1623] - IpcMemcachedProvider: Increase maxWaitCycles value