Roadmap

  • Plone 4.0 is a new major release of Plone, which builds on the Plone 3 release series.

    Plone 4 will focus on updates in the underlying Zope and Python technologies, substantial speed improvements, better support for large data volumes, and a variety of end-user features.

    A final release is to be expected during summer 2010.

    Improvement proposals included in this release:

    #7822
    Make standard file content types use ZODB BLOB support
    #8801
    Move action icon support into actions, deprecate CMFActionIcons
    #8802
    Move our upgrade / migration infrastructure to GenericSetup
    #8805
    Do not ship with NuPlone anymore
    #8808
    Require Python 2.5 or 2.6, Zope 2.12, and CMF 2.2 for Plone 4.0
    #8814
    Replace SecureMailHost with a standard Zope mailhost
    #8815
    Use normal CSS and no more magic base_properties
    #9186
    Set Image IDs from Title field
    #9214
    support logins using e-mail address instead of user id
    #9249
    Add TinyMCE as the default visual editor
    #9250
    Add jQuery Tools to base install
    #9256
    Expand variable substitution in mailing action of plone.app.contentrules
    #9258
    Replace Products.ATReferenceBrowserWidget with archetypes.referencebrowserwidget
    #9259
    Group dashboards
    #9263
    GenericSetup syntax for importing Sharing page roles
    #9264
    Merge backport patches from plone.app.dexterity into Plone
    #9272
    Exposing and editing Dublin Core properties
    #9285
    Show blocked portlets in management interface
    #9286
    Allow to show/hide portlets
    #9305
    Use real names instead of usernames
    #9309
    Better search for East Asian (multi-byte) languages.
    #9310
    User registration process more flexible
    #9314
    Plone "Developer Pack" option for installers
    #9315
    New theme for Plone 4
    #9316
    Unify folder implementations
    #9321
    Reimplement the search form with an eye on usability
    #9330
    Add ability to choose group when adding new site members
    #9545
    Folder Contents interface improvements
    #9560
    GroupUserFolder removing
    #9568
    Add buildout to the Plone Installer for Windows
    #9570
    Change root-of-Zope page for Unified Install
    #10014
    Enable sub-groups

  • Plone 4.1 is a minor release which builds on the improvements made in Plone 4.0.

    Improvement proposals included in this release:

    No results

    Improvement proposals being considered for this release:

    #9938
    factor custom output transformations out of the editors
    #10359
    Convert control panels to use z3c.form
    #10396
    allow option for using SSL login in form POST
    #10776
    Update to Zope 2.13
    #10804
    include workflow manager
    #10877
    Separate Products.CMFPlone from the Plone egg and its optional dependencies
    #10878
    Add "SiteAdmin" role
    #10900
    Use popup forms (overlays) for portlet editing
    #10901
    Set and enforce base coding standards for our own JavaScript

  • Milestone: 5.0

    Due in 13 months (10/01/11)

    Plone 5 is a major release that focuses on a new model for content authoring, better theming experience, and an improved type definition system.

    Although the Improvement Proposal process for Plone 5 hasn't started yet, a lot of the components that are slated for inclusion are available for experimental use in Plone 4. See Chameleon (faster template language), xdv (theming support), Dexterity (new type system) and Deco (content authoring and layout).

    The date for Plone 5 is still very tentative, so don't plan anything around it just yet.

  • This milestone is used to track bugs and other issues related to the 3.3.x series, and the progress bar has nothing to do with when the next 3.3.x release will ship.

  • This milestone is used to track bugs and other issues related to the 4.x series, and the progress bar has nothing to do with when the next 4.x release will ship.

  • Tickets assigned to the 'Future' milestone aren't targeted for inclusion in any specific release yet.

    For example feature requests that have no designated champion yet or are still under discussion are often in this milestone.

  • Milestone for ongoing improvements that aren't tied to a specific release. Documentation tasks are a good example of this.

Note: See TracRoadmap for help on using the roadmap.