Skip to main content

Home/ Plone distributed documentation/ Group items tagged major

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

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

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

  • confusion and false expectations
  • changed this policy
Graham Perrin

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

1 - 7 of 7
Showing 20 items per page