Skip to main content

Home/ Plone distributed documentation/ Group items tagged version

Rss Feed Group items tagged

Graham Perrin

Minutes, May 29, 2008 - Plone CMS: Open Source Content Management - 0 views

  • impact of faster 0.1 releases
  • messaging and perception
  • deprecation policy
    • Graham Perrin
       
      deprecation ≠ support
  • ...5 more annotations...
  • the intent is to support two major versions
  • our official policy is that we support the most recent two major versions
  • need to update version numbering policy
  • http://plone.org/documentation/manual/upgrade-guide/introduction
  • reflect current practices
Graham Perrin

Minutes, December 11, 2008 - Plone CMS: Open Source Content Management - 0 views

  • Supported versions
  • 2.5.5 has been marked “unsupported”
  • All board members
  • ...9 more annotations...
  • support two major versions
  • tacit policy
  • consider the lengthening of the release cycle
  • we’ve also spoken of 1-year support
  • definition
  • Security fixes
  • if technically feasible
  • we ask that the "unsupported" marker be removed from 25
  • Unanimously passed
Graham Perrin

Good coding practices - Plone CMS: Open Source Content Management - 0 views

  • traditionally supported the two most recent versions of Zope (2). This is generally a good model for add-ons to inherit: supporting the two most recent (major) versions
  • Plone 2.5 and Plone 3.x
  • contributions available to a much broader audience
Graham Perrin

On Plone documentation - Martin Aspeli - 1 views

  • I think it's a mistake to try and solve all the problems with "Plone documentation" in the same way
    • Graham Perrin
       
      +1
  • rely more on technology
  • What is current good practice?
    • Graham Perrin
       
      My initial reaction to this: get started | essential actions | refinements and current best practice …
  • ...20 more annotations...
  • a corpus small enough that it can be effectively reviewed
  • highlighted and easy to find
  • this is where they should be stumbling
    • Graham Perrin
       
      Can we elaborate on this point?
  • Barriers to entry should be low
  • version the document pertains to
    • Graham Perrin
       
      +1
    • Graham Perrin
       
      Re http://dev.plone.org/plone/ticket/7831 some simple triggers might draw attention to documentation that becomes outdated (or at least deserves review) at product update time.
  • concerned about how easy it is to add an article
  • highlight the "good" bits of documentation
  • reviewed at least each time we make a new Plone release
  • What's the right way to configure caching?
    • Graham Perrin
       
      Advice may be diverse.
  • If someone wants to contribute documentation, by all means let them!
  • allow comments
  • ratings of the type "was this helpful to you"
    • Graham Perrin
       
      I do often rate things (positively more often than negatively). However: I rarely observe other people's ratings.
  • Open the flood-gates
  • group documentation by audience, rather than by type
    • Graham Perrin
       
      I'm never wholly convinced about audience-based documentation.
    • Graham Perrin
       
      Can we group documentation by layer - through the Plone (TTP), Zope management interface (ZMI), file system et cetera?
  • Accept that how-to documentation won't be perfect
  • Add ratings
  • improve commenting
  • this is out of date
    • Graham Perrin
       
      Maybe "This is valid for version n.n of product x" plus "For more recent advice please visit …".
  • We should allow people to make requests for new documentation, and expose the wish list in a way that lets people vote for their favourite requests
    • Graham Perrin
       
      First improvements to a document might be: (1) a link to Trac, so that any documentation-related issue can be tracked; and (2) an in-document summary of relative tickets.
  • We have a Trac
Graham Perrin

Zope 3 Known Good Sets - 1 views

  • Zope 3.4.0 Released
  • January 29, 2009
  • integrates very well with the rest of the Python community
  • ...7 more annotations...
  • Zope 3 is now fully converted to an egg-based system
  • The Known Good Set (KGS)
  • a configuration of packages and their versions that are known to work well together
  • verified by running over twelve thousand tests on a daily basis
  • against Python 2.4 and 2.5 on the 32- and 64-bit platforms
  • "nail" the versions
    • Graham Perrin
       
      Is nailing analogous to pinning? In Plone community, I'm more familiar with the word 'pinning'.
  • KGS can be used in several ways
Graham Perrin

Why do none of the bookmarks refer to Plone support forums? - 6 views

The combination of Nabble embedded content + forced redirection to plone.org - in particular, the way in which all topics and all messages within a forum are represented as myriad anchors to a si...

started by Graham Perrin on 12 Nov 08 no follow-up yet
Graham Perrin

Saving the day: recovering lost objects - Jarn · Plone Solutions - 1 views

  • recovering lost objects
  • entire section of his site was missing
  • someone had deleted the object
  • ...26 more annotations...
  • 9 days earlier
  • Undo was no longer an option
  • Truncating the Data.fs (removing all transactions since, including the offending one)
  • undesirable
  • through RelStorage
  • time traveling: zc.beforestorage
  • small additional buildout configuration file
  • beforestorage.cfg
  • [buildout]extends = buildout.cfgeggs += zc.beforestorage ZODB3 zope.proxy[versions]ZODB3 = 3.8.1zope.proxy = 3.4.2[relstorage-patch]recipe = plone.recipe.commandcommand = cd ${buildout:eggs-directory}/ZODB3-3.8.1-py2.4-linux-i686.egg/ZODB curl -s http://svn.zope.de/zope.org/relstorage/tags/1.1c1/poll-invalidation-1-zodb-3-8-0.patch | patch -N -p0 cd ${buildout:directory}update-command = ${relstorage-patch:command}[instance]zope-conf-additional += enable-product-installation False
  • enable-product-installation
  • tells Zope not to try and write product information to the ZODB
  • because zc.beforestorage puts your ZODB in read-only mode
  • edit the zope.conf
  • <zodb_db main>    # Main database    cache-size 650000%import zc.beforestorage%import relstorage <before> before 2008-12-08T10:29:03    <relstorage>        <oracle>            dsn RELSTORAGE_DSN            password xxxxxxxxx            user xxxxxxxx        </oracle>    </relstorage> </before>    mount-point /</zodb_db>
  • impossible as the site stores
  • <before> before 2008-12-08T10:29:03    <relstorage>        <oracle>            dsn RELSTORAGE_DSN            password xxxxxxxxx            user xxxxxxxx        </oracle>    </relstorage> </before>
  • when you start the instance, you are in the past
  • found the lost object
  • Export/Import
  • save the export on the server
  • buildout with your regular buildout file
  • restart
  • import the .zexp
  • reindex the imported content
  • related data that lives outside of the object itself is gone
  • Martijn Pieters
Graham Perrin

Update your workflows to use GenericSetup profiles - Plone CMS: Open Source Content Man... - 0 views

  • Plone 2.1/2.0 (which are unsupported releases when Plone 3.0 is released)
Graham Perrin

Introduction - Plone CMS: Open Source Content Management - 0 views

  • confusion and false expectations
  • changed this policy
Graham Perrin

AkaSig » Blog Archive » Zope and Plone learning roadmap - 0 views

  • mastering Zope and Plone
  • newbies (like me) asking for information about the first steps
  • the diagram below is my guess on the ideal learning roadmap
  • ...5 more annotations...
  • Zope+Plone :
  • posted on Thursday, December 11th, 2003
  • pleased to have such an updated version available and I would share it
  • it would be great to find such a thing in the documentation section of plone.org
  • the more I learn Plone the more I see I have more to learn…
  •  
    The diagram is old (2003) but the presentation is thought-provoking.
Graham Perrin

When the Plone installer isn't enough - Immersive Training Experience - 0 views

  • ZopeSkel to get everything started
  • buildout that is based on the latest best practices
  • products and add-ons
  • ...9 more annotations...
  • 10 minute getting started
  • In this case, we want a Plone 3 buildout that grabs the latest stable version of Plone.
  • repeatable deployments
  • cd mysite
  • python bootstrap.py
  • buildout profiles that extend one another
  • paster create -t plone3_buildout mysite
  • predictable results
  • sure to get the same deployment every time you run bin\buildout
Graham Perrin

Mac OS X Manual Page For dscl(1) - 0 views

  • If no file path is provided then access goes only to the registered 1local nodes on the system
  • This manual page is for Mac OS X version 10.6
  • dscl -- Directory Service command line utility
  • ...8 more annotations...
  • may be a node name
  • PATH SPECIFICATION
  • If no file path is provided then access goes only to the registered local nodes on the system
  • local nodes
    • Graham Perrin
       
      plural
  • specify the plug-in
  • /LDAPv3/
  • or a Mac OS X Server (10.2 or later) host
  • specified by DNS hostname or IP address
1 - 12 of 12
Showing 20 items per page