Release.properties content changed for 2026-Q1.0 - is there a reason for it?

Development Tooling
1

Release 2026-Q1.0 is the only release which declares a general.availability.date, while all other releases declare a release.date.

Is this

  • a glitch or oversight?
  • a purposeful change in format, that will stay for future versions?
  • a semantic change that one should be aware of?

Asking for a tool that parses this stuff and gets confused…

Reference: From https://releases-cdn.liferay.com/dxp/2026.q1.0-lts/release.properties

app.server.tomcat.version=10.1.52
build.timestamp=1773755497
bundle.checksum.sha512=1d83bd434e70da59c543282fe59a0ce262b5f8845015ebfc030daa92ca06e1f7d16b8478d9cf017ea620e0b696754bd487029bd01d5d1fbff0c939982c3b52be
bundle.url=https://releases-cdn.liferay.com/dxp/2026.q1.0-lts/liferay-dxp-tomcat-2026.q1.0-lts-1773755497.7z
general.availability.date=2026-03-18
git.hash.liferay-docker=64599617f32db69b0a061438157c66316169a281
git.hash.liferay-portal-ee=987cbc98c3b7e405c7abc81e54b0177725be6df4
git.tag=2026.q1.0
liferay.docker.image=liferay/dxp:2026.q1.0-lts
liferay.docker.tags=2026.q1.0-lts
liferay.product.version=DXP 2026.Q1.0 LTS
target.platform.version=2026.q1.0
2

Hi @olafk,

Your answer is “a purposeful change in format, that will stay for future versions“. :slight_smile:

We changed it to be in line with the same terminology used on End of Life Policy | Liferay - Liferay DXP for release dates.

Thanks