Skip to main content

Home/ Plone distributed documentation/ Group items tagged release

Rss Feed Group items tagged

Graham Perrin

who wants to be release manager for Deliverance? - 0 views

  • Deliverance Discussion
  • who wants to be release manager for Deliverance?
  • Nov 29, 2009
  • ...33 more annotations...
  • The situation right now is dismal
  • private fork of the code if they want to make any modifications
  • getting a stable, maintained release of this 0.3 incarnation out the door
  • right now the bottleneck is on the maintenance side
  • it would be really nice to see deliverance moving to some dcvs
  • Deliverance tries to solve a problem that very few people have: styling an existing site without having to touch it
  • Plone where you would need hundreds of hours of work of skilled people to do a full styling
  • if you use Deliverance you still need to theme your Plone site
  • a lot of interest in Deliverance
  • XDV, since that is easier to deploy in non-Python environments
  • Deliverance + a proxy is obviously possible
  • legacy systems
  • "shrink-wrapped" solutions that they can't style
  • All my Plone projects these days use Deliverance or XDV
  • turn off most Plone stylesheets
  • custom stylesheet to augment the designer's styles
  • include the Plone authoring stylesheets more or less intact
  • new to Plone
  • teaching theming
  • new to Plone theming
  • comprehension and productivity
  • With Deliverance/XDV, I can get people who understand HTML + CSS to be productive with Plone
  • a *huge* win
  • hard to set it all up
  • soluble
  • stable 0.3 release out is of utmost importance
  • revisit the option of moving it to a different repository later
  • it only takes a very little bit of stop energy to get someone to go away
  • I hereby bestow upon Ethan the title of Maintainer
  • release now, and figure out code location etc later
  • DVCS's genuinely useful for including people in a development process
  • get git working with the major IDEs
  • I'd be looking at fewer man pages with hg than with git
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

Plone 3.1.1 released! - Plone CMS: Open Source Content Management - 0 views

  • If you're running older Plone 2.x sites and are unable to upgrade — make sure to follow some simple rules
Graham Perrin

Bug #415270 in collective.buildout: "Less memory hungry settings for plone.recipe.zope2... - 0 views

  • Less memory hungry
  • plone.recipe.zope2instance
  • Less memory hungry settings for plone.recipe.zope2instance
  • ...5 more annotations...
  • zodb cache site of 5000 objects
  • too much for servers of 512 MB - 768 MB memory (Plone 3.x)
  • suggest smaller cache
  • cache megabyte limiter
  • release notes
  •  
    Interesting. I'll experiment with my Plone 3.3.4 ZEO cluster on a G4 PowerPC Xserve, where physical RAM is limited to 2 GB …
Graham Perrin

Jon Stahl's Journal » Blog Archive » Plone 4: three times faster than Drupal,... - 0 views

  • Plone 4 is faster out of the box than some of the most common PHP platforms
  • three times faster than Drupal, Joomla and Wordpress
  • Plone 4
  • ...26 more annotations...
  • Jan 19th, 2010
  • Jon Stahl
  • Plone 4 is about to
  • enter beta testing prior to a final release
  • performance
  • out of the box
  • over three times faster
  • what does all this mean?  Well, honestly, not much
  • realistic sample content
  • very, very proud of Plone’s raw speed
  • suspect MAMP not to be very efficient
  • For read-only operations, once the objects have made it into ZODB’s object cache no database queries need be made
  • the difference is down to Plone’s use of the ZODB
  • Contrast this to the PHP/MySQL systems which must perform several selects in order to render the page
  • to fetch new objects it’s slower
  • ZODB fetches are serial
  • Archetypes persistent object design is far from optimal (page data is split over several persistent objects, slowing down load time)
  • addressed as part of Dexterity
  • fundamental architectural difference
  • CMSes that use the RDBMS and some kind of ORM or manual SQL (like Drupal, Joomla)
  • those that use an OODBMS such as Plone
  • ‘out of the box’ speed, since that is something a lot of people historically have not liked about Plone
  • less tuning needed to start with
  • even when caching is not applicable we still get the performance boost
  • our installer sets up ZEO with clients for you, so this is “out-of-the-box”
  • counter the (incorrect) perception out there that “Plone is slow”
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

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

  • Plone 3.1.4
  • no longer supported
    • Graham Perrin
       
      contentious
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

Zope 3 wiki FAQ - General - Known Good Set (KGS) - 0 views

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

Review of Veda Williams' Plone 3 Theming - ACLARK.NET, LLC - 0 views

  • Veda Williams'
  • Review
  • Plone 3 Theming
  • ...14 more annotations...
  • If you are interested in Plone and how Plone theming works
  • chapter by chapter review
  • I would have liked to have seen the PyPI features of plone.org mentioned
  • still hard to create Plone themes
  • tool for releasing themes (and any package) to both plone.org/products and pypi.python.org at the same time
  • http://pypi.python.org/pypi/jarn.mkrelease
  • Chapter 15 This chapter (by Alexander Limi) introduces people to "new style" theming
  • a while before it is fully digested
  • http://pypi.python.org/pypi/collective.xdv
  • great stuff but potentially confusing
  • XSLT transform "on the fly" (in memory)
  • but the recommended deployment strategy is to use NGINX or Apache with Laurence's patches
  • plone.org uses it
  • non-trivial to say the least
1 - 15 of 15
Showing 20 items per page