Ask Questions and Find Answers
Important:
Ask is now read-only. You can review any existing questions and answers, but not add anything new.
But - don't panic! While ask is no more, we've replaced it with discuss - the new Liferay Discussion Forum! Read more here here or just visit the site here:
discuss.liferay.com
RE: Liferay 7.2 Support How to track?
Hi all,
If I wanted to track the development of Liferay 7.2 support which github branch should I follow? I know there was an estimated release date of mid-summer and would just like to judge progress so we can plan a little better this side.
thanks
If I wanted to track the development of Liferay 7.2 support which github branch should I follow? I know there was an estimated release date of mid-summer and would just like to judge progress so we can plan a little better this side.
thanks
Hey Peter --I'm not sure if I have the right answer, but there is a 7.2.x branch https://github.com/liferay/liferay-portal/tree/7.2.x which, at the moment, has a commit from 7 hours ago. So it looks like it is actively being updated. I think Liferay also does a lot of "current development" on the master branch. With all that said, I don't know that you can use this to track progress towards a release. GA releases are not "guaranteed" as far as I know, but the unofficial goal is a yearly major release and then I think it's quarterly GA releases. If that is correct, then I would expect a G2 in early fall (like October timeframe). But this is all speculation of course

Hi Andew,
Thanks for the reply. I am aware of the github repo for liferay-portal and use that to track releases but I think the commerce extension is on a different release cycle and currently only support 7.1. Since I upgraded to 7.2 it broke the commerce extension. If I check out the github repo for the commerce extension on github there doesn't appear to be a 7.2 branch yet.
https://github.com/liferay/com-liferay-commerce
Any suggestions on how to track 7.2 support is welcomed.
Thanks for the reply. I am aware of the github repo for liferay-portal and use that to track releases but I think the commerce extension is on a different release cycle and currently only support 7.1. Since I upgraded to 7.2 it broke the commerce extension. If I check out the github repo for the commerce extension on github there doesn't appear to be a 7.2 branch yet.
https://github.com/liferay/com-liferay-commerce
Any suggestions on how to track 7.2 support is welcomed.
Hi Peter,
Liferay 7.2 compatibility for Commerce is still in progress. We've been working toward it on the 7.1 branch, actually -- right now we're hoping to have a single Commerce branch that's compatible with both Liferay 7.1 and 7.2 (though there's a chance this could change between now and feature-completion).
As far as I know, there's not a good way to track progress on this at the moment, unfortunately :/. I'll try to investigate this internally and let you know if I find a good way this can be done.
Liferay 7.2 compatibility for Commerce is still in progress. We've been working toward it on the 7.1 branch, actually -- right now we're hoping to have a single Commerce branch that's compatible with both Liferay 7.1 and 7.2 (though there's a chance this could change between now and feature-completion).
As far as I know, there's not a good way to track progress on this at the moment, unfortunately :/. I'll try to investigate this internally and let you know if I find a good way this can be done.
Hi Peter, I think you have your answer now but I wanted to apologize for my bonehead response. I foolishly glanced over the "Commerce" part (as in the category) and assumed that you were just talking about the portal itself. My bad -- though I did learn something. I thought that the Commerce 2.0 was already compatible with 7.2 -- another assumption I made because they were released together. Good to know that comparability is still a work in progress.
@Ethan, I can see in the Github repo there is a 7.1.x branch and also a 7.1.x-next branch. Can you explain the difference? is the -next version the one you reference here (working towards a 7.2 supported version)?
@Ethan, I can see in the Github repo there is a 7.1.x branch and also a 7.1.x-next branch. Can you explain the difference? is the -next version the one you reference here (working towards a 7.2 supported version)?
Hey Andrew,
The 7.1.x-next branch is our development branch, so that's where all our latest work is, and there are definitely no guarantees that it's particularly stable at a given time. 7.1.x is our release branch, so it roughly represents the state of our last release, plus (potentially) any important bugfixes that have gone in in the meantime.
For anyone working on top of the Commerce source code in the wild, I'd definitely recommend using 7.1.x as a rule (or even sticking to specific release tags and only upgrading when necessary), and only using 7.1.x-next for exceptional cases (e.g. trying out a new, not-yet-released feature you've been eager for).
The 7.1.x-next branch is our development branch, so that's where all our latest work is, and there are definitely no guarantees that it's particularly stable at a given time. 7.1.x is our release branch, so it roughly represents the state of our last release, plus (potentially) any important bugfixes that have gone in in the meantime.
For anyone working on top of the Commerce source code in the wild, I'd definitely recommend using 7.1.x as a rule (or even sticking to specific release tags and only upgrading when necessary), and only using 7.1.x-next for exceptional cases (e.g. trying out a new, not-yet-released feature you've been eager for).
This plugin is a portlet that exposes additional classes and methods that are not present in Liferay's out-of-the-box API. These additional classes and methods allow Liferay Screens to do certain operations that are needed for the screenlets to work correctly.
Copyright © 2025 Liferay, Inc
• Privacy Policy
Powered by Liferay™