Liferay Portal 6.2 Community Beta Program

Introduction and Goals #

Liferay relies on its open source community to help validate Liferay releases before they are generally available, to maximize quality before the release. Liferay follows an iterative software release cycle, with interim development builds (called Milestones), followed by a Beta period in which feature-complete builds are produced, and then finally one or more Release Candidate builds, one of which becomes the final release (called the first "GA" release).

For 6.2, the goal of this Liferay Community Beta Program is to validate the Beta-quality releases of Liferay, and ensure that it meets the needs of its community of enthusiasts, users, partners, customers, and developers. Feedback will be taken at high priority to ensure that issues discovered by our community program are considered and acted upon before the release.

Ideas for new features are always encouraged (and should be filed via the Ideas board), but keep in mind that to maintain high quality and the ability to release a solid product, large-scale changes and new features will likely have to wait until after the 6.2 release. Most important now is to look at the existing feature set and see if there are glaring bugs, major incompatibilities or other usability issues that should be considered to be fixed prior to GA.

Getting Involved #

The 6.2 Beta Program is free and is open to the entire community! To become a member of the 6.2 Beta Program, simply sign up and let us know which areas (tracks) in which you are interested in participating, and you will be add to the team and given specific instructions for each track you are interested.

We will also be giving small gifts to those that participate, to proudly show that you were involved in the 6.2 release! Also, for anyone that has contributed in the past, please add your name to the Community Contributor Hall of Fame!

Timeline #

  • Sign-up Period: August 5-12
  • Beta Testing Begins: August 12
  • Last day to file issues: September 27

Of course, you can file bugs after the cutoff date, but bugs coming in after this date may not get triaged or dealt with before the release.

Downloads #

The Beta Builds that the Community Beta program will use can be found below. You may need more than one of these to complete your testing!

Beta Program Tracks #

To better organize our efforts and ensure that we have good coverage of this release, we have broken the best testing into separate tracks.

TrackNameDescriptionQA Lead
Track 1Systems TestingBeta test Liferay in your system environment, paying particular attention to issues around Operating System, App Server, Database, Browser, JDK/JRE.TBD
Track 2New Features and Functionality TestingTest drive Liferay's new features before they are available.TBD
Track 3Integration and Compatibility TestingEnsure your apps and 3rd-party integrations are ready to go with the new release.TBD
Track 4Upgrade Testing Help improve the quality of Liferay Portal by testing the upgrade path from your current Liferay version.TBD

Each track will have a suggested set of activities/features/tasks that you will be expected to consider, for each track you are participating in. Each track will also have one or more Liferay QA Engineers assigned to help guide participants, file issues, and see them through to resolution.

New Feature Details #

  • Mobile (Site Preview, Responsive Themes, Device Recognition)
  • UI & UX (Bootstrap, Dockbar, Accessibility, other improvements)
  • WCM (Recycle Bin, ADT, Page Mgmt, WCM Admin, authoring improvements)
  • Staging (Validation, Offline Support)
  • Site Management (Membership, Hierarchical sites, cross-site sharing)
  • Document Management (Drag/Drop, Subscriptions, I18N of Doc Types)
  • Collaboration (Blogs, Wiki improvements)
  • Calendar (New UI, Resource scheduling, Multiple calendars)
  • Administration (Control Panel, Permission management)
  • Platform (OSGi, OAuth, Portlet Sandboxing, PACL, Web Services)
  • Developer (Liferay IDE, APIs, Themes)
  • Micellaneous (Search improvements, Batch content creation, 3rd party integrations)

The above are high-level feature areas of Liferay. If you want to know specifically (down to the granularity of each work ticket), check out the 6.2 Stories by Feature area. This is a hierarchical listing of each item representing change that went into the 6.2 beta release.

Known issues and limitations #

As the beta program progresses, major issues that participants should be aware of will be listed here (it is not an exhaustive list of all bugs found in Beta - for that, check out Beta Bug list).

Known beta issues:

  • The Welcome Page that was present in the earlier Milestones has been removed in the Beta-1 build, but there are plans to bring it back.
0 Attachments
13504 Views
Average (1 Vote)
The average rating is 3.0 stars out of 5.
Comments
Threaded Replies Author Date
I clicked on the 6.2 stories by feature area... Joseph Toman September 4, 2013 11:19 AM
Same here. Can't access even after signing up... Ryan Kennedy October 29, 2013 11:26 AM
Weird! I'll get it fixed and report back. James Falkner October 29, 2013 11:30 AM
Cool, thanks! [message] The requested operation... Ryan Kennedy October 29, 2013 11:36 AM
Specifically, when I'm logged in I get:... Joseph Toman October 29, 2013 12:25 PM
I also get same error "Structure with id 155... Ratnamala Mehetre November 10, 2013 6:17 PM
Apologies for the delay! I'm trying to find the... James Falkner November 11, 2013 7:30 AM
Ok, the structure board should be visible now... James Falkner November 12, 2013 7:24 AM

I clicked on the 6.2 stories by feature area and don't have permission to view it. I do have an account on issues.liferay.com.
Posted on 9/4/13 11:19 AM.
Same here. Can't access even after signing up & logging in.

Any other documentation? I've been asked to research some new features.
Posted on 10/29/13 11:26 AM.
Weird! I'll get it fixed and report back.
Posted on 10/29/13 11:30 AM in reply to Ryan Kennedy.
Cool, thanks!

The requested operation was not successful. Sorry about that! Error messages, if any, are given below.
Structure with id 155 does not exist or you don't have permissions to view it.
Posted on 10/29/13 11:36 AM in reply to James Falkner.
Specifically, when I'm logged in I get:
Structure with id 155 does not exist or you don't have permissions to view it.
Posted on 10/29/13 12:25 PM.
I also get same error "Structure with id 155 does not exist or you don't have permissions to view it.". When can we see this JIRA page?
Posted on 11/10/13 6:17 PM.
Apologies for the delay! I'm trying to find the right person to flip the right bits on the server. Stay tuned!
Posted on 11/11/13 7:30 AM in reply to Ratnamala Mehetre.
Ok, the structure board should be visible now (though you will still need to be logged in).
Posted on 11/12/13 7:24 AM in reply to James Falkner.