Permalink
Commits on Aug 12, 2016
  1. Added Plone 5.1 classifier to setup.py.

        [ci skip]
    mauritsvanrees committed Aug 12, 2016
Commits on Aug 8, 2016
  1. Back to development: 2.0.7

    [ci skip]
    mauritsvanrees committed Aug 8, 2016
  2. Preparing release 2.0.6

    [ci skip]
    mauritsvanrees committed Aug 8, 2016
  3. Cleaned up empty headers from changelog.

    [ci skip]
    mauritsvanrees committed Aug 8, 2016
Commits on Jul 6, 2016
  1. Merge pull request #5 from plone/gforcada-use-zope-decorators

    Use zope.interface decorator
    gforcada committed on GitHub Jul 6, 2016
Commits on Jul 5, 2016
  1. Use zope.interface decorator

    This not only makes code more pleasent to read,
    but also makes the code python 3 compatible
    (while maintaining python 2 compatibility).
    gforcada committed Jul 5, 2016
Commits on Feb 25, 2016
  1. Back to development: 2.0.6

    [ci skip]
    mauritsvanrees committed Feb 25, 2016
  2. Preparing release 2.0.5

    [ci skip]
    mauritsvanrees committed Feb 25, 2016
  3. Added keywords to setup.py.

    [ci skip]
    mauritsvanrees committed Feb 25, 2016
  4. Cleanup changelog.

    [ci skip]
    mauritsvanrees committed Feb 25, 2016
  5. Merge pull request #4 from plone/write-on-read

    Fix a write on read situation
    mauritsvanrees committed Feb 25, 2016
Commits on Feb 11, 2016
  1. check-manifest

    [ci skip]
    mauritsvanrees committed Feb 11, 2016
Commits on Feb 9, 2016
  1. Fix a write on read situation

    If the context gets its first annotation it need to be marked as
    safe to write.
    
    The same goes for the annotations on the object.
    gforcada committed Oct 21, 2015
  2. Added classifiers in setup.py.

    [ci skip]
    mauritsvanrees committed Feb 9, 2016
Commits on Dec 13, 2015
  1. Revert "Merge branch 'write-on-read'"

    This reverts commit c637f42, reversing
    changes made to 44a6c4f.
    gforcada committed Dec 13, 2015
  2. Merge branch 'write-on-read'

    gforcada committed Dec 13, 2015
  3. Fix a write on read situation

    If the context gets its first annotation it need to be marked as
    safe to write.
    
    The same goes for the annotations on the object.
    gforcada committed Oct 21, 2015
Commits on Nov 13, 2015
  1. Added CONTRIBUTING.rst.

    [ci skip]
    mauritsvanrees committed Nov 13, 2015
Commits on Oct 30, 2015
  1. Added New/Fixes headers to changelog.

    [ci skip]
    mauritsvanrees committed Oct 30, 2015
Commits on Oct 24, 2015
  1. Allowed union merge strategy in CHANGES.rst.

    [ci skip]
    mauritsvanrees committed Oct 24, 2015
Commits on Jul 27, 2015
  1. Rename README.txt to README.rst

    gforcada committed Jul 27, 2015
  2. Rename zcml.txt to zcml.rst

    gforcada committed Jul 27, 2015
  3. txt -> rst

    gforcada committed Jul 27, 2015
  4. Rename README.txt to README.rst

    gforcada committed Jul 27, 2015
  5. txt -> rst

    gforcada committed Jul 27, 2015
Commits on Aug 22, 2014
  1. Whitespaces cleanup

    gforcada committed Aug 22, 2014
Commits on Jan 28, 2014
  1. Back to development: 2.0.5

    esteele committed Jan 28, 2014
  2. Preparing release 2.0.4

    esteele committed Jan 28, 2014
Commits on Nov 6, 2013
  1. Merge pull request #1 from plone/recursive-rules

    Cascading rules
    tdesvenain committed Nov 6, 2013
Commits on Nov 4, 2013
Commits on Oct 26, 2013
  1. If a rule is 'recursive', actions executed by this rule

      can recursively trigger other rules.
    tdesvenain committed Oct 26, 2013
  2. If a rule is 'recursive', actions executed by this rule

      can recursively trigger other rules.
    tdesvenain committed Oct 26, 2013