I think what Chris is asking is to have NEWS entries in the branch
where a commit is done, no mater if the fix was already reported in a
previous branch NEWS file.

It'd mean instead of easy merge on release we'd have to have hard and time-consuming cleanup of old NEWS - I'd have to go through NEWS and for each entry go to 5.3 NEWS and check if it's there too and if it's there remove it. Or we'd just have it twice in both 5.3 and 5.4 sections? We need to figure it out btw as if we carry NEWS with patches in git that would mean patches will never cleanly apply between branches (as NEWS files are always different). We need to have a better mechanism for this.

BTW, why we don't put the same in the trunk NEWS then?
Stanislav Malyshev, Software Architect
SugarCRM: http://www.sugarcrm.com/
(408)454-6900 ext. 227

PHP CVS Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

Reply via email to