Re: [RFC] Release Process
| From: | Ferenc Kovacs | Date: | Tue, 23 Nov 2010 11:32:29 +0000 |
| Subject: | Re: [RFC] Release Process | ||
| References: | 1 2 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-50437@lists.php.net to get a copy of this message | ||
On Tue, Nov 23, 2010 at 11:07 AM, Derick Rethans <derick@php.net> wrote:
> On Mon, 22 Nov 2010, Felipe Pena wrote:
>
> > 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.
>
Why do you think that?
I can see two reason:
1) you think that the current rules/policies/methods are good enough.
2) you think that these rules/policies/methods aren't important for the
quality of the release.
both seems wrong from the past experiences of new php major/major.minor
releases.
see my last email in the other thread
>
> 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.
>
> What however goes straight against this is:
>
> * January
> o Decisions which features or changes will be in the next
> release
>
> You don't decide on it, you just have to go with what we have.
>
who decided that?
>
> All the rest you write in the RFC is basically already as we do it.
>
yeah, maybe, but they aren't written down, accepted and well-known rules, so
you can forgot/misunderstand/bend them. :/
Tyrael