Plone 4 work is underway

1 message

Eric Steele (esteele) () Plone 4 work is underway

Reply Threaded

Plone Users,

For those of you who don't know me, I'm your occasionally-friendly
neighborhood release manager (the Plone 4 one). As the development of
Plone 4 kicks off, I wanted to fill you in on just what's been going on.

Over the past week, the members of the Plone 4 Framework Team slogged
their way through evaluating a whopping 56 PLIPs (PLone Improvement
Proposals) for possible inclusion into Plone 4. I'm told that is the
highest number for any Plone release to date and I'm inclined to think
that this has a lot to do with our attempting a more open submission
process this time around. I'm very excited to see so many new
potential contributors.

The Framework Team, made up of David Glick, Calvin Hendryx-Parker,
Alec Mitchell, Ross Patterson, Raphael Ritz, Erik Rose, Laurence Rowe,
and Matthew Wilkes, deserves a huge round of applause for their
efforts in evaluating so many proposals to complete the initial voting
process in such a short amount of time. The voting breakdown is
available at http://spreadsheets.google.com/ccc?key=rR4UAIObeTZtdUExfYophHw
for those who are curious.

And so, the 40 proposals that have made the cut:

* Make standard file content types use ZODB BLOB support
http://dev.plone.org/plone/ticket/7822

* Move action icon support into actions, remove CMFActionIcons
http://dev.plone.org/plone/ticket/8801

* Move our upgrade / migration infrastructure to GenericSetup
http://dev.plone.org/plone/ticket/8802

* Do not ship with NuPlone anymore
http://dev.plone.org/plone/ticket/8805

* Require Python 2.5 or 2.6, Zope 2.12, and CMF 2.2 for Plone 4.0
http://dev.plone.org/plone/ticket/8808

* Replace SecureMailHost with a standard Zope mailhost
http://dev.plone.org/plone/ticket/8814

* Deleting a user should revoke roles
http://dev.plone.org/plone/ticket/8901

* Set Image IDs from Title field
http://dev.plone.org/plone/ticket/9186

* Support logins using e-mail address instead of user id
http://dev.plone.org/plone/ticket/9214

* Add TinyMCE as the default visual editor
http://dev.plone.org/plone/ticket/9249

* Add jQuery Tools to base install
http://dev.plone.org/plone/ticket/9250

* Expand variable substitution in mailing action of
plone.app.contentrules
http://dev.plone.org/plone/ticket/9256

* Replace Products.ATReferenceBrowserWidget with
archetypes.referencebrowserwidget
http://dev.plone.org/plone/ticket/9258

* Group dashboards
http://dev.plone.org/plone/ticket/9259

* GenericSetup syntax for importing Sharing page roles
http://dev.plone.org/plone/ticket/9263

* Merge backport patches from plone.app.dexterity into Plone
http://dev.plone.org/plone/ticket/9264

* Exposing and editing Dublin Core properties
http://dev.plone.org/plone/ticket/9272

* Improved search results presentation. A merge of:
http://dev.plone.org/plone/ticket/9282
http://dev.plone.org/plone/ticket/9271

* A more lightweight backend for collections
http://dev.plone.org/plone/ticket/9283

* Allow views to override skin layer elements easily
http://dev.plone.org/plone/ticket/9284

* Show blocked portlets in management interface
http://dev.plone.org/plone/ticket/9285

* Allow to show/hide portlets
http://dev.plone.org/plone/ticket/9286

* Improved commenting infrastructure
http://dev.plone.org/plone/ticket/9288

* Group management delegation
http://dev.plone.org/plone/ticket/9292

* Improved UI for collections
http://dev.plone.org/plone/ticket/9295

* Well formed, valid XHTML
http://dev.plone.org/plone/ticket/9300

* Improving the event type with recurrence, etc.
http://dev.plone.org/plone/ticket/9302

* Use real names instead of usernames
http://dev.plone.org/plone/ticket/9305

* Better search for East Asian (multi-byte) languages.
http://dev.plone.org/plone/ticket/9309

* User registration process more flexible
http://dev.plone.org/plone/ticket/9310

* Clean up of user related actions UI
http://dev.plone.org/plone/ticket/9311

* Plone "Developer Pack" option for installers
http://dev.plone.org/plone/ticket/9314

* New theme for Plone 4
http://dev.plone.org/plone/ticket/9315

* Unify folder implementations
http://dev.plone.org/plone/ticket/9316

* Reimplement the search form with an eye on usability
http://dev.plone.org/plone/ticket/9321

* Ensure that Plone 4 can upgrade Zope on Windows and Mac OS X via
binary eggs
http://dev.plone.org/plone/ticket/9322

* Unified interface for lists of content
http://dev.plone.org/plone/ticket/9327

* Content im-/export
http://dev.plone.org/plone/ticket/9328

* Manage actions through-the-plone
http://dev.plone.org/plone/ticket/9329

* Add ability to choose role when adding new site members
http://dev.plone.org/plone/ticket/9330

We now move on to the initial implementation period. The developers
who have submitted the above proposals will be hard at work over the
next six weeks writing the code to prove that their ideas belong in
the Plone core. There will then be a short review and revision period.
After that, the Framework Team will be tasked with conducting an in-
depth review of each submission to decide whether or not it's met
their criteria for inclusion into Plone 4.

The planned shipping date for Plone 4 is December 1st of this year.
This is a very aggressive timeframe, but I am confident that the Plone
developer community will rise to the challenge.

We welcome your comments and input as the process continues.

Thank you,
Eric

------------------------------------------------------------------------------
_______________________________________________
Plone-Users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/plone-users