> -----Original Message----- > From: Stas Malyshev [mailto:smalys...@sugarcrm.com] > Sent: Wednesday, November 24, 2010 9:39 PM > To: Derick Rethans > Cc: Felipe Pena; internals > Subject: Re: [PHP-DEV] [RFC] Release Process > > Hi! > > >> With the recent chaos in the way we begin and ended releases, we > >> would like to propose a clean way to deal with releases and related > >> decisions: [1] > > > > Really? I think you're blowing this all way out of proportion. > > > > I don't mind a yearly release cycle, as we should get out more releases. > > I don't mind a monthly release cycle for .z releases. > > I think the idea is not focusing on "yearly" or "monthly" but having some > predictable schedule. Nobody says it should be set in stone, let's be > realistic > here - if we need to slip a release here and there, we'd do it. But having > known > targets is the goal, not having releases "whenever somebody on the list wakes > up and decides to have a release". I think the project needs to grow up a bit > and > have at least some semblance of release schedule. The mere existence of it > written somewhere public would motivate people to adhere to it.
I agree with that. More structure and predictability will be very valuable to the project. We created a lot of structure in Zend Framework and it has really paid off. Btw, we don't have to look far. Just the change in having people document their suggestions via RFCs already had a substantial impact on this project both in terms of peer review and having a long lasting trail of what made it into a given release. More structure will typically yield in higher quality, more visibility and therefore more motivation for people to contribute, and I believe also in more deliverables rather than less as people will work towards clear goals + be accepting if they miss them and they need to wait for the next release train. Andi -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
