New release cycle is good
15Apr08
The new release cycle is, without a doubt, a big step forward for Plone. More regular and predictable releases will attract more attention for new features, and more visibility means new potential users. Making a major release last for a while, complemented with periodic upgrade releases, also contributes, ultimately, to a more robust code base.
Now we don’t have to wait for a year, or even more, for a new feature-rich release. There is, obviously, a lot to improve, but Plone-3.1, which includes a set of handy features like new portlets, dependency handling in GenericSetup and more, is already a clear evidence of the new release cycle success.
Filed under: Plone | 2 Comments
Tags: Plone, release




I’d like to add that the fast 0.0.1 increment release schedule is also tremendous. Knowing that there will be another bug-fix release in a month helps take the pressure off of each release. And, that helps them get done on time. So we get constant quality improvement in already solid releases.
Great work, Wiggy!
Yes, I didn’t mention, but to have bug-fix releases every month is also one big achievement. Plone looks more robust and predictable in time.