Liferay 7

[darren rose, modificado hace 9 años.]

[font=Wingding

When will Liferay 7 be available?

[David H Nebinger, modificado hace 9 años.]

They had originally said q3, but one never knows. It's a major change (jquery versus yui for the base, OSGi integration, etc).

If you're asking when you should start deploying it, well I say it's best to let it back in for 6 mos to a year after release. You want to let the release bake in, let folks find the bugs in the initial release, and allow Liferay a chance to resolve the bugs.

Just like 6.0.0, it had issues at first release. At 6.0.6 it stabilized to a point that the remaining bugs could be worked around, but that wasn't the case for some of the earlier ones.

Those that waited had a much easier upgrade and runtime experience that the initial adopters...

[Olaf Kock, modificado hace 9 años.]

Yes. (couldn't resist)

Here's the definitive answer on any release date that's predicted for the future.

And seriously: Is there anything specifically that you're waiting for? Or just the version bump? Some will wait until 7.0 comes out only to ask when 7.1 is scheduled to be out. Should you wait for 7.0? No. Implement now, upgrade later. Get started sooner rather than later. You'll be able to make good use of the portal until then, and improve further when the platform updates.

[Arif Rahman, modificado hace 9 años.]

Has there been any decisions on what the upgrade path will be? For example, will there be a direct upgrade path for 6.0 and 6.1 or will the base install need to be 6.2.

Maybe it's too early ask, just curious.

Thanks!

[David H Nebinger, modificado hace 9 años.]

Liferay typically does a "cumulative" upgrade path. So if you are on 6.0 and upgrade to 6.2, the 6.1 changes are applied first. Keeps things simple from an upgrade perspective because you just have to worry about the layers and not all of the possible derivations of an actual upgrade.

Unless they break character (which doesn't appear so in the milestones) a similar upgrade path will be in place.

Note however that this is just for the data directory and the database. Your custom plugins, of course, will be up to you to upgrade. You'll have to deal with all of the theme changes, javascript changes, and API changes.

[James Falkner, modificado hace 9 años.]

David H Nebinger:

Liferay typically does a "cumulative" upgrade path. So if you are on 6.0 and upgrade to 6.2, the 6.1 changes are applied first. Keeps things simple from an upgrade perspective because you just have to worry about the layers and not all of the possible derivations of an actual upgrade.
.

In some cases, you can go directly from 6.0 to 6.2:

"Liferay introduced the seamless upgrade feature with Liferay 6.1. Seamless upgrades allow Liferay to be upgraded more easily. In most cases, pointing the latest version of Liferay to the database of the older version is enough."

So it's possible that you'll be able to go from 6.1 to 7.0 directly, but I do think it's pretty early to know for sure.

[Olaf Kock, modificado hace 8 años.]

...also: Even when it's "possible": In case you're running into issues, it might be easier to debug if you identify the problem's location: If the update to 6.1 already fails, there's no way another upgrade to 6.2 or 7.0 will fix it. Not that anybody typically runs into those problems...

[darren rose, modificado hace 8 años.]

Olaf Kock:

Yes. (couldn't resist)

Here's the definitive answer on any release date that's predicted for the future.

And seriously: Is there anything specifically that you're waiting for? Or just the version bump? Some will wait until 7.0 comes out only to ask when 7.1 is scheduled to be out. Should you wait for 7.0? No. Implement now, upgrade later. Get started sooner rather than later. You'll be able to make good use of the portal until then, and improve further when the platform updates.

OSGI support

regards