-1. I genuinely believe at least one core plugin that utilizes the blocks should be bundled with core, which seems technically a "feature". All core themes now support blocks, and to further that being a focus of how plugins interact with themes, a public release should foster that. All good intentions aside, we don't know when the next release will be, and not providing the base elements for that, we would be stymying that evolution.
Once a core plugin is introduced that provides some basic blocks, I'm for a release and would be +1. If the cabal and community do not believe such plugin is an additional "feature" rather expounding on an existing feature, that's fine. I just think something should be included. ~miklb On Jan 31, 2011, at 10:34 PM, Michael C. Harris wrote: > Step one on the Release Checklist[1], freeze by merging trunk to > makaanga (the branch that bears fruit). This represents a freeze of > new features to focus bug fixing in preparation for a 0.7 release. > According to the Release Policy[1], as this is a Major Point Release, > we will freeze for at least a week. > > This is the list of remaining bugs for 0.7: > https://trac.habariproject.org/habari/report/10 > > So let's VOTE for a freeze to start the release of 0.7. > > > > > [1] http://wiki.habariproject.org/en/Release_Checklist > [2] http://wiki.habariproject.org/en/Release_Policy > > -- > Michael C. Harris, School of CS&IT, RMIT University > http://twofishcreative.com/michael/blog > IRC: michaeltwofish #habari > > -- > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to > [email protected] > For more options, visit this group at > http://groups.google.com/group/habari-dev -- To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/habari-dev
