Over the past week, the members of the Framework team slogged their
way through 56 PLIPs, which I'm told is the highest number for any
Plone release. The FWT deserves a huge round of applause for their
efforts in completing the initial voting process in such a short
amount of time. The full voting breakdown is available [1] for those
who are curious.
And so, the 40 proposals that have made the cut:
* Make standard file content types use ZODB BLOB support
https://dev.plone.org/plone/ticket/7822 * Move action icon support into actions, remove CMFActionIcons
https://dev.plone.org/plone/ticket/8801 * Move our upgrade / migration infrastructure to GenericSetup
https://dev.plone.org/plone/ticket/8802 * Do not ship with NuPlone anymore
https://dev.plone.org/plone/ticket/8805 * Require Python 2.5 or 2.6, Zope 2.12, and CMF 2.2 for Plone 4.0
https://dev.plone.org/plone/ticket/8808 * Replace SecureMailHost with a standard Zope mailhost
https://dev.plone.org/plone/ticket/8814 * Deleting a user should revoke roles
https://dev.plone.org/plone/ticket/8901 * Set Image IDs from Title field
https://dev.plone.org/plone/ticket/9186 * Support logins using e-mail address instead of user id
https://dev.plone.org/plone/ticket/9214 * Add TinyMCE as the default visual editor
https://dev.plone.org/plone/ticket/9249 * Add jQuery Tools to base install
https://dev.plone.org/plone/ticket/9250 * Expand variable substitution in mailing action of
plone.app.contentrules
https://dev.plone.org/plone/ticket/9256 * Replace Products.ATReferenceBrowserWidget with
archetypes.referencebrowserwidget
https://dev.plone.org/plone/ticket/9258 * Group dashboards
https://dev.plone.org/plone/ticket/9259 * GenericSetup syntax for importing Sharing page roles
https://dev.plone.org/plone/ticket/9263 * Merge backport patches from plone.app.dexterity into Plone
https://dev.plone.org/plone/ticket/9264 * Exposing and editing Dublin Core properties
https://dev.plone.org/plone/ticket/9272 * Improved search results presentation. A merge of:
https://dev.plone.org/plone/ticket/9282 https://dev.plone.org/plone/ticket/9271 * A more lightweight backend for collections
https://dev.plone.org/plone/ticket/9283 * Allow views to override skin layer elements easily
https://dev.plone.org/plone/ticket/9284 * Show blocked portlets in management interface
https://dev.plone.org/plone/ticket/9285 * Allow to show/hide portlets
https://dev.plone.org/plone/ticket/9286 * Improved commenting infrastructure
https://dev.plone.org/plone/ticket/9288 * Group management delegation
https://dev.plone.org/plone/ticket/9292 * Improved UI for collections
https://dev.plone.org/plone/ticket/9295 * Well formed, valid XHTML
https://dev.plone.org/plone/ticket/9300 * Improving the event type with recurrence, etc.
https://dev.plone.org/plone/ticket/9302 * Use real names instead of usernames
https://dev.plone.org/plone/ticket/9305 * Better search for East Asian (multi-byte) languages.
https://dev.plone.org/plone/ticket/9309 * User registration process more flexible
https://dev.plone.org/plone/ticket/9310 * Clean up of user related actions UI
https://dev.plone.org/plone/ticket/9311 * Plone "Developer Pack" option for installers
https://dev.plone.org/plone/ticket/9314 * New theme for Plone 4
https://dev.plone.org/plone/ticket/9315 * Unify folder implementations
https://dev.plone.org/plone/ticket/9316 * Reimplement the search form with an eye on usability
https://dev.plone.org/plone/ticket/9321 * Ensure that Plone 4 can upgrade Zope on Windows and Mac OS X via
binary eggs
https://dev.plone.org/plone/ticket/9322 * Unified interface for lists of content
https://dev.plone.org/plone/ticket/9327 * Content im-/export
https://dev.plone.org/plone/ticket/9328 * Manage actions through-the-plone
https://dev.plone.org/plone/ticket/9329 * Add ability to choose role when adding new site members
https://dev.plone.org/plone/ticket/9330The initial PLIP implementation deadline is set for end-of-day Sunday
August 16. That gives you lucky winners 6 weeks to get your working
code in for the first round of reviews. The Framework Team asks that
those of you who feel that you'll not be able to complete your work in
that amount of time note such on your PLIP tickets so that they can
decide how best to proceed.
This time around, we'll be using mr.developer to keep track of PLIP
buildouts. Instead of creating individual buildouts, I'm asking
everyone to share the Plone 4.0 dev buildout [2], using a
separate .cfg file to extend buildout.cfg for each PLIP. See [3] for
an example. To use/evaluate a specific PLIP, include that PLIP's cfg
file by running something like "bin/buildout -c plips/plip9901-
myplip.cfg". Branch existing packages where needed. This process
should help us all avoid the pain of merging as David Glick finalizes
the migration to Zope 2.12.
The Framework Team has also asked that you get your implementations in
ASAP. As it stands now, each of the 8 FWT members will be responsible
for an in-depth review of at least 10 proposal implementations, so any
extra time you can allow them is not just greatly appreciated, but
also crucial to getting this release out on time.
We would also like to see progress updates on each PLIP ticket from
our implementers. For those of you working in the plone SVN, you can
attach your commit messages to the PLIP ticket by including a "refs
#0000" in your commit message. We'll be prodding you with varying
levels of severity for status reports as the weeks roll on.
We have a basic schedule of milestones [4],[5] that I'll be keeping
updated.
Eric
[1]
http://spreadsheets.google.com/ccc?key=rR4UAIObeTZtdUExfYophHw[2]
https://svn.plone.org/svn/plone/buildouts/plone-coredev/branches/4.0/[3]
https://svn.plone.org/svn/plone/buildouts/plone-coredev/branches/4.0/plips/plip9316-unified-folders.cfg[4]
http://bit.ly/plone4calendar[5]
http://bit.ly/plone4ical------------------------------------------------------------------------------
_______________________________________________
Plone-developers mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/plone-developers
