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.
--
Stanislav Malyshev, Software Architect
SugarCRM: http://www.sugarcrm.com/
(408)454-6900 ext. 227
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
