On 03/07/2012 10:15 AM, Stas Malyshev wrote:
Hi!
Users should be able to see the fixes in 5.4 by reading only 5.4 NEWS.
That's why we merge 5.3 news before the release.
See my other email. This is error prone since bugs may not be
relevant, and release cycles may not coincide. I'd like
On 03/07/2012 10:22 AM, Stas Malyshev wrote:
Hi!
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-co
On Wed, Mar 7, 2012 at 7:22 PM, Stas Malyshev wrote:
> Or we'd just have it twice in both 5.3 and 5.4 sections?
Yes
> BTW, why we don't put the same in the trunk NEWS then?
I would say we could consider to add NEWS entry after a 1st release
for a given branch?
Cheers,
--
Pierre
@pierrejoye
Hi!
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 thr
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.
On Wed, Mar 7, 2012 at 7:15 PM, Stas Malyshev wrote:
> Hi!
>
>
>> Users should be able to see the fixes in 5.4 by reading only 5.4 NE
Hi!
Users should be able to see the fixes in 5.4 by reading only 5.4 NEWS.
That's why we merge 5.3 news before the release.
I think the 5.3& 5.4 branches have to be considered distinct from now
on.
What's different now?
--
Stanislav Malyshev, Software Architect
SugarCRM: http://www.sugar
On 03/07/2012 10:00 AM, Stas Malyshev wrote:
Hi!
This one (#61173) isn't in 5.4 NEWS, since it was only fixed in 5.3.11.
Do we now duplicate 5.3 and 5.4 NEWS?
Users should be able to see the fixes in 5.4 by reading only 5.4 NEWS.
I think the 5.3 & 5.4 branches have to be considered distin
Hi!
This one (#61173) isn't in 5.4 NEWS, since it was only fixed in 5.3.11.
Do we now duplicate 5.3 and 5.4 NEWS?
--
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
On 03/07/2012 08:06 AM, Christopher Jones wrote:
On 3/6/12 11:38 PM, Stanislav Malyshev wrote:
stas Wed, 07 Mar 2012 07:38:57 +
Revision: http://svn.php.net/viewvc?view=revision&revision=323985
Log:
MFH: Fixed bug #61173 (Unable to detect error from finfo constructor).
Bug: https://bu
On 3/6/12 11:38 PM, Stanislav Malyshev wrote:
stas Wed, 07 Mar 2012 07:38:57 +
Revision: http://svn.php.net/viewvc?view=revision&revision=323985
Log:
MFH: Fixed bug #61173 (Unable to detect error from finfo constructor).
Bug: https://bugs.php.net/61173
stas Wed, 07 Mar 2012 07:38:57 +
Revision: http://svn.php.net/viewvc?view=revision&revision=323985
Log:
MFH: Fixed bug #61173 (Unable to detect error from finfo constructor).
Bug: https://bugs.php.net/61173 (Assigned) Unable to detect error from finfo
con
11 matches
Mail list logo
