Blogs

Release Process Changes

Michael Young

December 06, 2007

Less Than a Minute Read

We had a long conversation at the office regarding release process, versioning, etc, that we'll be presenting at the LA retreat this year.

But in a nutshell the goals were to:

- increase timeliness
- improve the quality
- lock down features
- have a LTS / EOL plan for incremental micro (x.y.z)/ minor (x.y)releases
- formalize a QA process
- start a beta testing program

5.0 will be almost exclusively PC 2.0 (JSR-286) upgrade and WSRP 2.0 and sample plugins excercising these upgrades. There will be bug fixes and minor features of course.

5.1+ will be the build out of the other focused product lines and core improvements, including to but not limited to:

- workflow
- business intelligence
- enhanced clustering, terracotta and standalone
- security
- social networking apps (producer / consumer)
- remote staging

Many of these features are sponsored by our customers, clients, and the community. Please contact us if your organization would like to sponsor a new feature and we'll get it on the roadmap.

If you are interested in participating in the beta testing program, please let us know!

Jorge will be expanding in more detail some of the things we talked about during our brainstorm session.

4 Comments

Please sign in to comment.

Hi Michael,

a few questions.

a) Is version 5 no longer going to separate the portlets from the core? This was a big point often mentioned on the forums and I know that the plan was to separate the core from the portlets. Is this gone now as a plan?

b) Do you have any indicative timelines for version 5 and version 5.1?

c) Can you expand on the idea for the social networking apps.

d) Can you expand on your plan for security...is it something like using acegi?

thanks and regards,
Brian

Please sign in to reply.

a) we still do plan to separate the portlet, but not until 5.1 or 5.2

b) 5.0 currently slated for feb, 5.1 for april

c) we're looking at ways to allow liferay consume and publish to facebook, igoogle, and support for open social

d) we're going to go through the points listed on the owasp.org top 10 and make sure we have them all down.

Please sign in to reply.

Hi Michael,

is there a chance that the configuration of Liferay will be more easy? I'm hoping for a database store of the configuration. This would allow for real-time changes from inside the portal (like changing the e-mail server, allowd files for the document library, upload size, etc).
As a nice side effect, using a DB for storing the configuration would also allow to set up 1 central Conf-DB for all Liferay systems in a landscape (dev, test, qa, pre-prod, prod, maint) and to transport a configuration change throught the landscapes. This would also allow for a more easy adoption of ITIL and COBIT.

Thanks and best regards,
Tobias

Please sign in to reply.

Hi Michael,

Scheduler is not working in 5.1.2 and 5.0.2

i am using staging and publish a page from stage to live and do some changement in scheduler, page is not published if i do some changement in scheduler.

please reply me
is it bug?

Thanks
Nidhi Singh

Please sign in to reply.