Tue, 31 Jul 2012 16:16:50 +0200 prepare version 3.14.9 oldstable cubicweb-version-3.14.9
Pierre-Yves David <pierre-yves.david@logilab.fr> [Tue, 31 Jul 2012 16:16:50 +0200] rev 8503
prepare version 3.14.9
Tue, 31 Jul 2012 17:32:54 +0200 [composite] apply composite on new enty too (closes #2450679) oldstable
Pierre-Yves David <pierre-yves.david@logilab.fr> [Tue, 31 Jul 2012 17:32:54 +0200] rev 8502
[composite] apply composite on new enty too (closes #2450679) Before this changesets, automatic deletion did not applied to entity created in the same transaction. This patch remove this filtering in the dedicated operation. The original filtering where introduced by 5d889b4928bb but no rational where found for this changes. The former behavior is seen as inconsistent and creates bug in some cubes.
Tue, 31 Jul 2012 17:25:28 +0200 [storage] relies on event=='deleted' to detect "delete" event (closes #2450680) oldstable
Pierre-Yves David <pierre-yves.david@logilab.fr> [Tue, 31 Jul 2012 17:25:28 +0200] rev 8501
[storage] relies on event=='deleted' to detect "delete" event (closes #2450680) When we delete a previously edited entity, it *will* have a cw_edited attribute even if the goal is to delete it. The function get an argument that explicitly contains the "delete" event. The code now uses that instead.
Tue, 31 Jul 2012 11:04:45 +0200 [composite] apply composite on new enty too stable
Pierre-Yves David <pierre-yves.david@logilab.fr> [Tue, 31 Jul 2012 11:04:45 +0200] rev 8500
[composite] apply composite on new enty too Before this changesets, automatic deletion did not applied to entity created in the same transaction. This patch remove this filtering in the dedicated operation. The original filtering where introduced by 5d889b4928bb but no rational where found for this changes. The former behavior is seen as inconsistent and creates bug in some cubes.
Tue, 31 Jul 2012 10:57:03 +0200 [storage] relies on event=='deleted' to detect "delete" event stable
Pierre-Yves David <pierre-yves.david@logilab.fr> [Tue, 31 Jul 2012 10:57:03 +0200] rev 8499
[storage] relies on event=='deleted' to detect "delete" event When we delete a previously edited entity, it *will* have a cw_edited attribute even if the goal is to delete it. The function get an argument that explicitly contains the "delete" event. The code now uses that instead.
Tue, 31 Jul 2012 11:19:11 +0200 [web navigation] previous / next icons are missing mandatory alt attribute stable
Sylvain Thénault <sylvain.thenault@logilab.fr> [Tue, 31 Jul 2012 11:19:11 +0200] rev 8498
[web navigation] previous / next icons are missing mandatory alt attribute
Tue, 31 Jul 2012 10:12:06 +0200 [testlib] consider rset for template / view selection (closes #2447183) stable
Adrien Di Mascio <Adrien.DiMascio@logilab.fr> [Tue, 31 Jul 2012 10:12:06 +0200] rev 8497
[testlib] consider rset for template / view selection (closes #2447183) The original code did something like: kwargs['rset'] = rset viewfunc = lambda **k: viewsreg.main_template(req, template, **kwargs) kwargs.pop('rset') return self._test_view(viewfunc, view, template, kwargs) meaning that by the time ``viewfunc`` (i.e. the lambda function) is called, ``rset`` was popped from ``kwargs`` and had no chance to be passed to ``main_template``.
Tue, 24 Jul 2012 17:51:00 +0200 [documentation] fix some ReST compilation problems
Adrien Di Mascio <Adrien.DiMascio@logilab.fr> [Tue, 24 Jul 2012 17:51:00 +0200] rev 8496
[documentation] fix some ReST compilation problems
Tue, 24 Jul 2012 15:06:55 +0200 [test] remove no more necessary attribute cache manipulation to repair test
Sylvain Thénault <sylvain.thenault@logilab.fr> [Tue, 24 Jul 2012 15:06:55 +0200] rev 8495
[test] remove no more necessary attribute cache manipulation to repair test
Tue, 24 Jul 2012 11:19:16 +0200 [entity] more tweaks for entity attribute cache handling on cw_set/cw_create to fix test regression
Sylvain Thénault <sylvain.thenault@logilab.fr> [Tue, 24 Jul 2012 11:19:16 +0200] rev 8494
[entity] more tweaks for entity attribute cache handling on cw_set/cw_create to fix test regression * when an attribute is listed in dont-cache-attrs, purge any previous value * test value is actually modified in EditedEntity.__setitem__ before adding attribute to dont-cache-attrs
(0) -3000 -1000 -300 -100 -10 +10 +100 +300 +1000 +3000 tip