Re: [RFC] Release Process
| From: | Derick Rethans | Date: | Tue, 23 Nov 2010 14:58:29 +0000 |
| Subject: | Re: [RFC] Release Process | ||
| References: | 1 2 3 4 5 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-50458@lists.php.net to get a copy of this message | ||
On Tue, 23 Nov 2010, Ferenc Kovacs wrote:
> On Tue, Nov 23, 2010 at 2:59 PM, Derick Rethans <derick@php.net> wrote:
>
> > On Tue, 23 Nov 2010, Ferenc Kovacs wrote:
> >
> > > > 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. :/
> >
> > And I don't think that is a bad thing. It's good to be able to be
> > flexible.
> >
> Its good for you, but its bad for the people, who expect you to follow the
> rules, you know, the vendors, developers, etc.
Well, vendors don't follow rules in the first place. They just add
random patches anyway. Developers are pretty much aware what a bug fix,
security bug fix and development tree means. With an annoucement (which
should really be a regular thing, sortof) of a new minor release, isn't
it clear? In case you say no, don't write an RFC that requires really
strict following, but instead write guidelines that match current
practise.
Derick
--
http://derickrethans.nl | http://xdebug.org
Like Xdebug? Consider a donation: http://xdebug.org/donate.php
twitter: @derickr and @xdebug