Blog

On Monday, 7 October 2024, the Technical Steering Committee for the Laminas Project held its monthly meeting. The topics discussed included:

• Creating a marketing and outreach committee.
• Hiring a dedicated developer for the Laminas and Mezzio repositories.

We detailed the meaning and some inner workings of Continuous Integration (CI) in a previous article, so here we will focus on what happens after CI completes successfully.

CI is followed by Continuous Delivery (CD) which gets the code ready for deployment to the production or staging environment. This ensures that the code is ready to be released manually. Continuous Deployment goes one step further and automates the release itself. The development team has to decide on what CD is right for them, but in both cases the end result is more frequent and reliable software updates.

Continuous Integration (CI) involves the frequent merging of code updates from developers into a shared codebase. This can be done as often as those updates are ready to be reviewed. Once the CI process is finalized, Continuous Delivery (CD) automatically deploys the code to the production environment. This flow streamlines the development process for faster and more reliable releases.

The Laminas Project has created a large number of packages to serve the needs of the PHP community. But what happens when you need to make sure that the package you want to use in your application is being actively maintained? Sure, you can check each package manually, but the most useful thing would be a full overview of this vital information.

The Technical Steering Committee for the Laminas Project has decided to mark Laminas API Tools (formerly Apigility) as security-only, indicating that no new features or enhancements will be developed and only security-related updates will be provided going forward. This decision is made in light of the evolving landscape of web API development and the desire to ensure that users have access to modern, fully supported tools. As an alternative, the committee recommends Dotkernel API, a robust and actively maintained framework that offers enhanced features, better performance, and ongoing support to meet the needs of developers. This recommendation aims to facilitate a smooth transition for users seeking a reliable and future-proof solution for their API development needs.

On Monday, 4 March 2024, the Technical Steering Committee for the Laminas Project held its monthly meeting. The topics discussed included the visibility of maintenance decisions and the optional dependency of laminas-servicemanger in certain components.

Version 8.3 of PHP was released on 23 November 2023, with nice improvements and new features such as typed class constants and the new function json_validate.

The support for version 8.3 was added to the components of Laminas and Mezzio.

Today, the Linux Foundation formally announced that it now hosts the Laminas Project!

Our charter became effective on March 24, 2020.

This also means that you can now donate to the project via CommunityBridge. Our goal is to raise enough money initially to help fund somebody to work part-time on the project.

As our various worldwide economies begin opening up following the COVID-19 outbreak, we will also renew our search for entities interested in funding via a corporate membership model, which will help provide funding longevity to the project.

A huge thank you everybody who has helped make this step in the project's evolution possible!

On Monday, 6 April 2020, the Technical Steering Committee for the Laminas Project held its second monthly meeting. An agenda was crowd-sourced amongst the TSC members prior to the meeting, and the meeting was held in the Laminas Slack.

You can find the minutes in the TSC repository.

A brief summary of decisions follows.

Back in October 2018, Rogue Wave Software announced reorganization of its Zend portfolio, including Zend Framework. The Zend Framework community was understandably shaken, and many were concerned about the future of the framework. Six months later, in April of 2019, Rogue Wave announced they would be transferring the project to the Linux Foundation as the Laminas Project.

A couple months before this announcement, in February 2019, we started working on a tool for transferring the project repositories to their new homes. At the beginning, everyone thought the tool should be relatively simple, as we "just" needed to change namespaces. But our goal was much greater: we wanted to provide packages fully compatible with legacy Zend Framework components. We wanted our new components to replace legacy components (yes, we wanted to use replace in composer.json).

We needed a tool capable of much more than just "rewriting namespaces".