Re: [Framework-Team] Re: [plone4] Release process

On Dec 27, 2008, at 13:31 , Ross Patterson wrote: It seems like this this dump format will likely become a point of hackability in our software ecosystem. People out there will find interesting things to do with it aside from dump-and-reload. This would be a good thing except we're *expecti

Re: [Framework-Team] [plone4] Release process

On Dec 25, 2008, at 12:08 , Hanno Schlichting wrote: This means I want to get Plone to the point where we use iterations (probably about two months) and make sure we have a working software at the end of those and ship them as a preview release. A very enthusiastic +1. Merge early, merge of

Re: [Framework-Team] Re: PLIP lifecycle

On Dec 28, 2008, at 5:23 , Tom Lazar wrote: i particularly like the notion of using workflow states as 'reminders' to make sure aspects aren't missed. OTOH, workflow states are serial, and it'd be a shame to force teams to do their evaluations in a specific order.

[Framework-Team] Re: PLIP lifecycle

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Erik Rose wrote: > On Dec 28, 2008, at 5:23 , Tom Lazar wrote: > >> i particularly like the notion of using workflow states as >> 'reminders' to make sure aspects aren't missed. > > OTOH, workflow states are serial, and it'd be a shame to force tea

[Framework-Team] Multiple workflows (Was: PLIP lifecycle)

Tres Seaver wrote: You can actually have multiple workflows for a given type. I may be the only person who has ever actually used the feature, but it is truly helpful at times. I'd be interested to hear what kind of situations it's useful for? Martin -- Author of `Professional Plone Develo

Re: [Framework-Team] Multiple workflows (Was: PLIP lifecycle)

Previously Martin Aspeli wrote: > Tres Seaver wrote: > > >You can actually have multiple workflows for a given type. I may be the > >only person who has ever actually used the feature, but it is truly > >helpful at times. > > I'd be interested to hear what kind of situations it's useful for? I

Re: [Framework-Team] Re: PLIP lifecycle

On Jan 2, 2009, at 14:33 , Tres Seaver wrote: OTOH, workflow states are serial, and it'd be a shame to force teams to do their evaluations in a specific order. You can actually have multiple workflows for a given type. I may be the only person who has ever actually used the feature, but it

[Framework-Team] Re: Multiple workflows (Was: PLIP lifecycle)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Martin Aspeli wrote: > Tres Seaver wrote: > >> You can actually have multiple workflows for a given type. I may be the >> only person who has ever actually used the feature, but it is truly >> helpful at times. > > I'd be interested to hear what kin

[Framework-Team] 3.3 reviews

Could someone remind me of when we need to have review bundles for 3.3 ready and when the code review process kicks off? Martin -- Author of `Professional Plone Development`, a book for developers who want to work with Plone. See http://martinaspeli.net/plone-book

[Framework-Team] NuPlone and Plone 3.2

Hi, Why on earth is Products.NuPlone not in the Plone 3.2 egg? Is this in purpose or just a gross oversight? Martin -- Author of `Professional Plone Development`, a book for developers who want to work with Plone. See http://martinaspeli.net/plone-book ___

Re: [Framework-Team] 3.3 reviews

Deadline for bundles is Saturday Jan. 17 and the first round of reviews will be done by Jan. 31, according to this thread: http://n2.nabble.com/Plone-3.3-update-td1488610.html On Jan 2, 2009, at 7:57 PM, Martin Aspeli wrote: Could someone remind me of when we need to have review bundles for

Re: [Framework-Team] NuPlone and Plone 3.2

On 3 Jan 2009, at 02:16, Martin Aspeli wrote: Why on earth is Products.NuPlone not in the Plone 3.2 egg? In partial answer,