Pull Requests / Release Trains

[jgruenewald]

Hi Dev-Team,

I currently have some open GitHub-PR’s which I proposed to the master-branch.
I suppose that means that when these Pull-Requests get merged they will be part of the next major-release only (and not maintenance release).

Is there a fixed release cadence for major-releases (are there any plans for when the next major release will be due)?

As we’re eager to have those changes implemented is it advisable / accpeted practice to also propose Pull-Requests to the 19.1 branch (Release Train) in order to have them implemented in a next maintenance release?

Cheers Jan

[RalfBecker]

Hi Jan,

I suppose that means that when these Pull-Requests get merged they will be part of the next major-release only (and not maintenance release).

Yes

Is there a fixed release cadence for major-releases (are there any plans for when the next major release will be due)?

No, currently we are working on stabilizing eTemplate2 and app.js parts ported to TypeScript.

One big feature for the new release is using push notifications for all changes to get instant updates without the need to constantly poll the server.

Plan was to get the next release in summer, but our development focus currently moved to more short-term targets to improve home-office szenarios using EGroupware (see yesterdays webinar 🇩🇪 Webinar EGroupware Smart Working: neue Funktionalitäten in German).

Ralf