- Update to 4.1.4 For Committer's reference: http://tb.s.ubze.ro//logs/7.4-FreeBSD-i386/py27-Products.CMFPlone-4.1.4.log http://tb.s.ubze.ro//logs/7.4-FreeBSD-amd64/py27-Products.CMFPlone-4.1.4.log http://tb.s.ubze.ro//logs/8.2-FreeBSD-i386/py27-Products.CMFPlone-4.1.4.log http://tb.s.ubze.ro//logs/8.2-FreeBSD-amd64/py27-Products.CMFPlone-4.1.4.log http://tb.s.ubze.ro//logs/9.0-FreeBSD-i386/py27-Products.CMFPlone-4.1.4.log http://tb.s.ubze.ro//logs/9.0-FreeBSD-amd64/py27-Products.CMFPlone-4.1.4.log Port maintainer (zope@FreeBSD.org) is cc'd. Generated with FreeBSD Port Tools 0.99_5 (mode: update, diff: ports)
Responsible Changed From-To: freebsd-ports-bugs->zope Over to maintainer (via the GNATS Auto Assign Tool)
Muhammad Moinur Rahman wrote on 19.04.2012 01:18: >> Number: 167075 >> Category: ports >> Synopsis: [PATCH] www/py27-Products.CMFPlone: update to 4.1.4 Hi Muhammad, before you go further with PR's, I want be sure that you know about version pinning for plone 4.1.4: http://dist.plone.org/release/4.1.4/versions.cfg Plone is quite fragile on dependencies versions, so they all should be updated at once and to particular ones that is listed in versions.cfg and only after throughout testing on live plone installation, so you can't just update it to latest version and expect that nothing will be broken with it. I'm on my half-way to updating plone to 4.1.4 (and adding plone "metaport") but still need some time to finish and test. -- Regards, Ruslan Tinderboxing kills... the drives.
State Changed From-To: open->closed Closed after discussion with submitter. Plone 4.1.5 is out and I'm working on update