Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:54839
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain lsces.co.uk from 213.123.26.187 cause and error)
Message-ID: <4E54A84B.1060108@lsces.co.uk>
Date: Wed, 24 Aug 2011 08:29:15 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:6.0) Gecko/20110815 Firefox/6.0 SeaMonkey/2.3
MIME-Version: 1.0
To: PHP internals <internals@lists.php.net>
References: <4E510339.3000609@thelounge.net> <CAEZPtU7+QBPFWVk7iZ5RfU6b999zNNe1wpX-5Lv7gOpvCpepsQ@mail.gmail.com> <4E51078E.1000401@thelounge.net> <CAEZPtU7WKucxQ-Nus+2JGCXutKrqfKETVH8d=uz237itxxq6Ww@mail.gmail.com> <4E520DAC.1090609@oracle.com> <4E5212BD.50306@thelounge.net> <CAEZPtU4W7H92GYEdUHpsiZXxmUkQa+GsfoO25DKqP4dGmWzRSQ@mail.gmail.com> <4E52226C.8030400@lsces.co.uk> <4E522A37.6050301@thelounge.net> <4E5238C7.6040206@lsces.co.uk> <4E523A7F.1040700@thelounge.net>
In-Reply-To: <4E523A7F.1040700@thelounge.net>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Failing Autotests / Bugs
From: lester@lsces.co.uk (Lester Caine)

Reindl Harald wrote:
>> Actually this is possibly another argument for a properly managed DVCS setup? On other projects I can pick
>> >  critical commits and apply them, and it flags when other bits need to be implemented as well. Almost does away
>> >  with the need to produce actual releases, but you do need to differentiate security fixes from simple 'improvements'?
> this has really nothing to do with DVCS
>
> a patch is security-critical or not and if he is atomic enough to be sure that
> there are no big side-effects to expect it woulld be really fine to include
> it directly on the download-page with short-decritpion and date

This was really a heads up for those who are working on _how_ the DVCS system 
would work in practice. Managing the code contained in a security patch is just 
as important as any other change, and if something is critical then it has to be 
in the main codebase anyway? With the correct setup, _you_ could locally manage 
your RPM builds in parallel, and as critical patches appear you get a heads up 
if you need them? And your local DVCS will track changes to the SPEC-file and 
which patches apply?

-- 
Lester Caine - G8HFL
-----------------------------
Contact - http://lsces.co.uk/wiki/?page=contact
L.S.Caine Electronic Services - http://lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk//
Firebird - http://www.firebirdsql.org/index.php